Contribute/Recognition

Recognizing volunteers for their contributions will deepen and extend relationships and will help us develop casual contributors into core contributors.

Recognition can be an item like a badge or can be a recognition of potential by helping volunteers develop through mentoring and training.

Say Thanks

A simple note of thanks is a great way to recognize someone.

• email
• blog post: https://blog.mozilla.org/community/category/spotlight/
• postcard
• etc.

Badges

Making badges at badges.mozilla.org

• I work at Mozilla. How do I make a badge?
• Where do I host it and how?

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

Recommendation: Swag is special and the process of sending swag out to contributors shouldn't be automated the same way that badges are issued. We recommend creating opportunities for your team to regularly consider who you would like to recognize by sending a shirt, mug, etc. These regular reminders could be done by:

• Add an agenda item to regular team meetings asking for nominations for volunteers who have made important contributions recently. Make sure to include link to the GearStore wiki page so people know where to go to get delivery scheduled.

• Update the badges.mozilla.org site to send notifications to point people when people earn a certain badge. This wouldn't be used to automatically issue swag, but would be a useful reminder for team members to consider nominations for contributors who you'd like to recognize. (Note: this feature doesn't exist now on badges.mozilla.org).

• Create a regularly recurring contributor spotlight, such as the Reps of the month program

Where to schedule delivery for swag: 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.

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.

• File:Student Contributor Letter.pdf (PDF file)
• File:Student Contributor Letter.odt (ODT file)

There is also a template form for a completion letter that documents what activities have been accomplished by the student.

• File:Contributor Completion Letter.odt (ODT file)

Invitation to Mozillians

Inviting a contributor to mozillians.org, our community directory, is a great way to recognize someone and also get them better connected with Mozilla. This directory is a resource to make it easy for Mozillians to learn who is involved, what they do and how to connect with them. It also allows contributors to receive email communications from Mozilla with important news and announcements.

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