-
-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Mozilla Open Badges to replace coderwall #1704
Comments
There's been suggestions in the past for Mozilla's OpenBadges.org: #1646 (comment) and #1008 (comment). |
@hugovk open badges would be wonderful, I don't have any experience with integrating them myself but if someone wants to tackle it I'd be happy to add them |
My concern about OpenBadges is that it seems like a lot of implementation work just for a cool picture to be generated that we'd have to design ourselves (sorry badge fans!). If we could make the OpenBadges meaningful in a way that properly integrates with Mozilla's vision of how they should work, plus has some additional meaning on our side (e.g. unlocks something cool, triggers an event) then it would be worthwhile, IMHO. |
Looked into it, and I agree with @xadamy, looks like it takes a lot of work to be a badge issuer. |
If it's massively complex I'm happy to ignore them for now and add something else in there for this year. |
Mozilla are now suggesting 24pullrequests as an activity on Mozilla Campus Clubs: https://campus.mozilla.community/activities/ I think we can put the effort in to become a badge provider, it can't be that tricky surely? |
I found a ruby gem that might help too: https://github.com/ericallam/OpenBadges |
Since we removed the coderwall badges we'll need something else to add to the top section on the homepage to keep it feeling balanced.
The text was updated successfully, but these errors were encountered: