Confirmed users
371
edits
Thunderbird:Open Badges: Difference between revisions
→Tasks that Earn Badges: add "Core Contributor" badge criteria
Prawsthorne (talk | contribs) |
(→Tasks that Earn Badges: add "Core Contributor" badge criteria) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 20: | Line 20: | ||
# We define and design a set of badges. | # We define and design a set of badges. | ||
# We create the JSON blobs that contain the metadata regarding issuer, criteria, etc. | # We create the JSON blobs that contain the metadata regarding issuer, criteria, etc. | ||
# We use Mozilla Badge Baker to embed the JSON in the PNGs. | # We use Mozilla Issuer API (Badge Baker) to embed the JSON in the PNGs. | ||
# We use Mozilla's Backpack to store | # We use Mozilla's Backpack for earners to store their badges. | ||
So, assuming that the above process is correct, is this model correct? | So, assuming that the above process is correct, is this model correct? | ||
# We select a Thunderbird add-on author (or support or KB or Ambassador contributor) to whom we want to award a badge. | # We select a Thunderbird add-on author (or support or KB or Ambassador contributor) to whom we want to award a badge. | ||
# We create a JSON blob that describes the badge and the recipient, etc, and use the Badge Baker to create the PNG. | # We create a JSON blob that describes the badge and the recipient, etc, and use the Issuer API (Badge Baker) to create the PNG. | ||
# We email the newly baked badge to the recipient, who will upload the PNG to their Mozilla Badge Backpack | # We email the newly baked badge to the recipient, who will upload the PNG to their Mozilla Badge Backpack | ||
| Line 34: | Line 33: | ||
These are some ideas about the criteria we might use to reward badges: | These are some ideas about the criteria we might use to reward badges: | ||
* '''Thunderbird Core Contributor Badge''': People who contribute a significant patch to the Thunderbird core, thus demonstrating a competency in programming. | |||
* '''Thunderbird Add-on Developer Badge''': People who create a Thunderbird add-on that is accepted by AMO, thus demonstrating a competency in programming. | * '''Thunderbird Add-on Developer Badge''': People who create a Thunderbird add-on that is accepted by AMO, thus demonstrating a competency in programming. | ||
* '''Thunderbird Knowledge Base Author Badge''': People who create a Thunderbird Knowledge Base article that uses a set of the more complex formatting tools (templates, tables, images, etc), thus demonstrating a competency in authoring on a wiki platform and technical writing. | * '''Thunderbird Knowledge Base Author Badge''': People who create a Thunderbird Knowledge Base article that uses a set of the more complex formatting tools (templates, tables, images, etc), thus demonstrating a competency in authoring on a wiki platform and technical writing. | ||
| Line 58: | Line 58: | ||
* Thunderbird is the badge issuer. | * Thunderbird is the badge issuer. | ||
** We would create badges through OpenBadger (or, if we want to do this before OpenBadger is ready | ** We would create badges through OpenBadger or [http://badg.us/en-US/ a Mozilla approved badge creator like badg.us] (or, if we want to do this before OpenBadger is ready and don't want to use badg.us or other 3rd party badge issuer) we could manually build our badges | ||
* Thunderbird contributors are the badge earners | * Thunderbird contributors are the badge earners | ||
** We would have to "manually" issue their badges (as opposed to having the badges automatically issued when earners successfully complete an exam or something like that) | ** We would have to "manually" issue their badges (as opposed to having the badges automatically issued when earners successfully complete an exam or something like that) | ||
| Line 71: | Line 71: | ||
* We manually create badges (need graphic and dev input, but not a huge thing) | * We manually create badges (need graphic and dev input, but not a huge thing) | ||
* We manually issue badges (as described above) | * We manually issue badges (as described above) | ||
* Earners can display their badges on the websites or on Mozilla | * Earners can display their badges on the websites or on other supported social media sites from their instance of the Mozilla Open Badge Backpack | ||
== Longer-term Implementation == | == Longer-term Implementation == | ||
| Line 87: | Line 87: | ||
* Badge: a graphic file (PNG) that contains validation information about the Issuer, Earner, etc | * Badge: a graphic file (PNG) that contains validation information about the Issuer, Earner, etc | ||
* Issuer: organizations that issue badges | * Issuer: organizations that issue badges | ||
* Issuer API: JavaScript library that facilitates baking and issuing of badges | |||
* Earner: people who perform tasks and earn a badge | * Earner: people who perform tasks and earn a badge | ||
* Displayer: website that displays an earner's badge | * Displayer: website that displays an earner's badge | ||
| Line 97: | Line 98: | ||
* [http://openbadges.org/en-US/ Open Badges site] (links to high-level overviews of the players (issuers, earners, displayers) | * [http://openbadges.org/en-US/ Open Badges site] (links to high-level overviews of the players (issuers, earners, displayers) | ||
* [https://wiki.mozilla.org/Badges/Onboarding-Issuer Specifications for Issuers] | * [https://wiki.mozilla.org/Badges/Onboarding-Issuer Specifications for Issuers] | ||
* [https://github.com/mozilla/openbadges/ OpenBadges] in github | |||
* [https://github.com/mozilla/openbadger/wiki OpenBadger] in github | * [https://github.com/mozilla/openbadger/wiki OpenBadger] in github | ||
* [[Badges/About|About Open Badges Mozilla Wiki Page]] | |||
* [[Badges/GetStarted|Getting Started with Badges Mozilla Wiki Page]] | |||
* [http://criticaltechnology.blogspot.com/search/label/openbadges Peter Rawsthorne's blog posts on Open Badges] on criticaltechnology.blogspot.com | |||