Closed Bug 835934 Opened 7 years ago Closed 7 years ago
This is a tracker bug for getting badges.mozilla.org launched. This is a project to stand up a mozilla-wide badge creation and issuing service.
More details: I currently run badg.us  on my own server as a demo of django-badger . It's gotten popular, especially among educators. I'd like to transfer it to mozilla infra and relaunch as badges.mozilla.org. From there, I'd like to give it official attention and continue to develop it as a community platforms project. As of this comment, there's a dev server , a staging server that can't be updated by devs , and no production server. : https://github.com/lmorchard/badg.us/ : https://github.com/lmorchard/django-badger : https://badgus-dev.allizom.org/ : https://badgus.allizom.org/
There's also a backlog of github issues, which might someday be interesting to transfer to bugzilla (or not): https://github.com/lmorchard/django-badger/issues
Just got Chief setup on staging (bug 823672), so I think all that's left for this bug is the production deployment (bug 835941). Almost there...
Oh also, per bug 835943 the sites got renamed, so these are the new URLs: http://badges-dev.allizom.org (dev) http://badges.allizom.org (stage)
Looks like badges.mozilla.org is launched and operational, as far as I can tell! There are a couple of lingering ops issues, but not worth blocking this bug. I'll note them here, if only so I can remember: * bug 844278 (staging IRC bot dumping HTML into IRC during a push) * bug 844287 (dev & stage not sending me error emails)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.