Waiting on a reply for this, as I don’t know myself so I reached out to someone I know would.
I made the request but they didn’t get back to me. I’ll re-ping.
You keep saying that Webdev cares about this plugin, but I don’t see any evidence of that. They don’t even return your emails and you are the one they hired to give support.
WebDevStudios is in an agreement to help with support for Credly products. I am part of the team at WebDevStudios, and work on many projects within WebDevStudios, not just support and not just BadgeOS. Credly and their affiliates also has their own things going on that isn’t 100% BadgeOS every week.
I sent a reminder email about this, and we’ll see about a response soon, tomorrow at the earliest, as it’s the weekend.
I don’t mean to beat you up. You have been very good at replying. I just want to get you the help you need. If I need to pick up the phone and make some calls I am willing to do that. This could be a ground breaking plugin. I’m not as worried about the bugs as I am them loosing interest in it after we committed ourselves. If we decide to use this it will be by far your largest implantation. We would need to scale it to hundreds of thousands of users and millions of readers. And that’s just our reader base now. We could be very helpful putting both BadgeOS and Credly on the map.
Anyway, like I said thanks for your help, but we really need to light a fire under the decision makers if we are going to make this work.
Mozilla’s spec indicates that the “images should be square and not
exceed 256kb. They should have dimensions not smaller that 90 x 90.”
Credly recommends: images that are .jpg, .png, or .gif files under
2MB. For best results, use a square .png file with a transparent
background, at least 600×600 pixels. Credly will automatically resize
images to be Mozilla spec-compliant at the time badges are sent to
Mozilla Backpack (or other compatible systems that may be added in the
future).
The badges gets baked by Credly at the time badges are shared with
Mozilla’s Backpack via Credly. This ensures that the earner’s desired
and confirmed email address gets baked with the instance of their
earned badge.
The core BadgeOS team works directly with groups doing innovative,
custom and/or large scale implementations. Based on the size of the
project you describe, it sounds like you should connect directly with
the team to introduce yourself and be on the team’s radar. Reaching
out will also allow you to learn about some of the existing
large-scale deployments and inform the ongoing BOS development path
with your needs. Please drop a note to the team at:
http://badgeos.org/contact/ They will reply today.
