Contribute/Recognition

Recognition Guide

Badges

In Production

• State of the Union: Mozilla Badges (Good summary of active badge projects at Mozilla as of May 7, 2013)

In Process

• Engagement badges
• IT badge designs: http://cl.ly/image/1e3t0h1F093t and http://cl.ly/image/403E170C3t0J
• Creative Collective badge designs (from old Creative Collective site): http://www.flickr.com/photos/musingt/3811604179/in/set-72157617765620270
• More: https://openbadges.etherpad.mozilla.org/Internal-Moz-badge-issuers

Notes

Official badges from a Mozilla team vs. fun badges from individual Mozillians

How to measure if your badges are effective.

Other

• Notes on other people interested in issues badges:
• Friend of the Tree, invitation to events, Credits, spotlight blog post, LEAD, module owner/peer, timeline of contributions...

Measuring Effectiveness

There are a few things to consider when measuring the effectiveness of your badge program:

• What are your goals? Are you interested in growing contributors or retaining contributors (ie, stopping churn)?
  • This is likely to be tied to the maturity of your community. New communities just getting started will likely be interested in growth (ie, there is not much of an existing community yet to need to worry about retention) and more established communities will likely be interested in retention (ie, their processes have evolved where they have pathways to get new people involved and they want to keep people engaged)
  • The answer to this determines how you analyze the data (ie, a new community can have a simpler approach to analytics that doesn't try to manage both the entrance of new contributors and the exit of existing contributors becoming inactive)

• What's a meaningful time frame for growth? Can a new contributor progress through the set of contributor activities for your project in days, weeks, months. For instance, a new Firefox coding contributor would take multiple releases to go through the process of getting their development environment set up, finding a good bug, creating a patch, going through review process, etc.

• Since badges are opt-in, can you combine the data about who chose to accept a badge and who was eligible for one but didn't accept it? Could these two groups act as separate cohorts for a twin study?

Gear

https://wiki.mozilla.org/GearStore

Case study: AMO points and incentives program

School Credit

Officially vouching for contributions can be a very powerful way to recognize student volunteers who would like to receive school credit for their efforts.

Standard verification letters from academic institutions often contain language that we can't accept though. For example, language that references an internship can't be used to verify volunteer contributions.

Academic institutions want to find good learning experiences for their students and they may be willing to work with us to modify their acceptance letters. Dia created the following template student contribution letter after working with a University to change the language in their standard form.

• File:Student Contributor Letter.pdf (pdf)

Feel free to use this template as a starting point for a discussion with an academic institution you'd like to partner with to recognize existing student contributors or to create a source of future contributors.

Learning Resources

We can give contributors access to various learning resources: Rosetta Stone, Safari, LEAD/TRIBE, etc.

More

Recognition brainstorming exercise from Community Builders meetup at MozCamp Asia in 2012: https://etherpad.mozilla.org/contributor-recognition-brainstorm