-
Notifications
You must be signed in to change notification settings - Fork 263
Home
Hi, welcome to the Mozilla OpenBadges wiki. For an overview of the OpenBadges project, and to earn your first OBI compliant badge, see OpenBadges.org. If you want to play around with Mozilla's hosted version of this code, you can create your own Badge Backpack at beta.openbadges.org.
This wiki is focused on documenting the Open Badges Infrastructure reference implementation (OBI). This code runs beta.openbadges.org, and acts as the pipes that keep the larger badges ecosystem humming. The goal of the code (and the project) is to provide a user-centric backpack that allows badge earners to collect OBI compliant badges from multiple badge issuers. The user then has the option of displaying the badges wherever they'd like.
A full list of wiki pages is available here. Depending on your reasons for being here, these pages are probably useful,
- If you want to understand the assertion system.
- If you want to bake a badge.
- If you want to issue a badge.
- If you want to display a badge.
- Some tech focused FAQ's, acts as a supplement to our larger openbadges.org FAQ.
If you're interested in contributing to the project (hurray! you should!) the place to start is the official README. Join our Google Group, and look for us on IRC at irc.mozilla.org/6667 #badges, specifically the tech team:
- Brian Brennan (tech lead) brianloveswords
- Mike Larsson (developer) stenington
- Chris McAvoy (product lead) cmcavoy
You can also jump in right away by picking up a ticket and working on it. We've marked a handful of tickets as "Volunteer On-boarding," which is a reasonable place to jump in and get started. However, if you're really into it, feel free to just pick up a big issue and run with it. Make sure you comment in the issue so we know you're working on it.
If you're new to contributing to an open source project on Github, start here - How to fork a Github repository. Once you've made your changes to your fork, send them to us as a pull request, mentioning the issue you're addressing in the pull request description.