-
Notifications
You must be signed in to change notification settings - Fork 55
Migrate away from badgekit #1092
Comments
see also #1055 |
hey @Wardormeur I thought you were only using the baking API; are you also using badgekit server and the client? |
I guess so :) |
Nope, the baking tool is (IIRC) a tool to bake information into a png. A badge as such is a png with some metadata (data like the person it was awarded to, who awarded it, an evidence url, and so forth). The baking API just does that. Unless things have changed in the last number of months, which is quite possible, Zen only used to use baking (but I might be wrong). Hosting (and awarding) badges is part of what we do in PaperBadger and for that we need a full badges server (badgekit-api) and a client(badgekit-api-client). As you mention in this thread, they are not maintained, so we are migrating. So my question is, do you use baking and persona to push badges to a backpack, or you host and award the badges on your own infrastructure? The openbadges spec is huge, and the terminology can be rather tricky and confusing. |
Ah, thanks for the details, lots of docs i definitiley need to read (just found the "Assertions definition" links from backpack, which are insightful :)) |
I see, so you are running badgekit-api as part of your infra; then yeah, a migration is in order! :) |
How about a hackhaton (& beers !) ? :) |
That'd be cool too! :) There's also http://24pullrequests.com/events |
updated to add format description of badges |
Badgekit is dead and burried, but now even Persona is giving up.
Instead of trying to maintain an abandoned soft by ourselves, migrate to badgr which seems still active.
TODOS:
Some references :
https://github.com/concentricsky/badgr-server for production
https://github.com/josmas/local-badgr-server for
mozillascience/PaperBadger#159
The text was updated successfully, but these errors were encountered: