This page documents conversion points for different parts of the project to provide information about the contributor lifecycle for the Grow Mozilla dashboard. See bug 736109 for details about implementing this and see The SuperStar Radar blog post for information about why this is helpful for community building.
There are two things we'd like to show here to help us understand how easy or hard it is for people to contribute to certain parts of Mozilla.
The first measurement shows each step of the process involved from expressing interest in contributing to successfully completing a contribution. The following example graph shows how we'll be able to see where people are dropping out of the process so that we can identify and fix problems.
The second measurement shows how the percentage for each conversion point changes over time. This will allow us to see how effective a giving optimization has been.
- (A) shows lagging patterns - the wave train in successive transitions would lag in time.
- (B) shows how a major new release might bump up midlin contributor activity
- (C) shows how we might expect the population of top contributors to be more or less stable
- (D) shows some theoretical mass contributor fatigue
Note: The color of these boxes corresponds to activity level of contributor as defined in Who Is In The Mozilla Community? infographic.
- Yellow: Casual Contributor
- Orange: Active Contributor
- Green: Core Contributor
Note: As someone passes from casual to active contributor, we should look at way to send out automated invitation to the phonebook.
Note: There are 13 points for Coding listed below but the wiki can cut some of the content off. If you're not seeing all 13 points, make the window wider or decrease the font size.
|Functional Area||Conversion Point #1||Conversion Point #2||Conversion Point #3||Conversion Point #4||Conversion #5||Conversion #6||Conversion #7||Conversion #8||Conversion #9||Conversion #10||Conversion #11||Conversion #12||Conversion #13|
|Coding||Creating Bugzilla account||Getting editbugs access||Submitting patch||Having patch be approved||Having patch checked in||Gaining Level 1 commit access||Submitting 5 patches||Providing patch feedback / Conducting reviews||Gaining Level 3 commit access||Checking in your own code to repo||Pushing someone else's code to repo||Mentoring a bug||Becoming a module owner or peer|
|Recognition||Postcard and sticker set.|
|Functional Area||Conversion point #1||Conversion point #2|
|Support||Creating SUMO account||Engaging in SUMO activities|
Note: The exact definition of the levels can be found here
|Functional Area||Activity Level #1||Activity Level #2||Activity Level #3||Activity Level #4|
|Support||Creating SUMO account||4 answers on forum/edit 1 article in KB/l10n 1 KB article||10 answers on forum/edit 5 article in KB/l10n 5 KB article||30 answers on forum/edit 5 article in KB/l10n 5 KB article|
|Webdev||Fork a site repo||Submit a pull request||1 pull request merged||10 pull requests||25 pull requests||50 pull requests||100 pull requests||Mentored a bug that got resolved fixed|
|Recognition||Badge||Badge & ?||Badge & Invitation to Mozillians.org||Badge & ?||Badge & ?||Badge & ?||Badge & ?||?|
|2012 Conversions*||? (hundreds-thousands)||? (hundreds)||137||38||20||9||0||?|
|QA (Bug wrangler: Onboarding)||Create an account on Bugzilla using Persona||Create an account on job board on One and Done QA taskboard||Comment on 3 bugs in bugzilla.mozilla.org to add useful information||Complete a task on the One and Done taskboard||Participate in a QA testday||Get canconfirm status in Bugzilla||Change the status of 3 bugs in Bugzilla||Comment on 7 bugs in Bugzilla|
|Data source||Bugzilla new account||One and Done new account||Bugzilla comments||One and Done actions||Bugzilla QA whiteboard field (historic: whiteboard field)||Bugzilla user info (permissions)||Bugzilla status||Bugzilla comments|
|Recognition||Bugzilla account badge||(One and Done account badge)||Bugzilla action badge||(One and Done Action badge)||(QA Testday badge)||(Nothing)||(Bug Helper badge)||(Bug Party badge, make this one funny)|
|QA (Manual testing with MozTrap, Onboarding)||Create an account on MozTrap using Persona||Create an account on job board on One and Done QA taskboard||Pass or Fail three tests from MozTrap (can we have/do we need this level of specificity? )||Complete a manual testing task on the One and Done taskboard||Create a Bugzilla account||Participate in a QA testday (tag a bug in Bugzilla with the testday whiteboard tag)||Work on three bugs from a QA testday||Work on 7 bugs from a QA testday|
|Data source||MozTrap new account||One and Done new account||MozTrap actions||One and Done actions||Bugzilla new account||Bugzilla QA whiteboard field (historic: whiteboard field)||Bugzilla QA whiteboard field (historic: whiteboard field)||Bugzilla QA whiteboard field (historic: whiteboard field)|
|Recognition||(badge)||(One and Done account badge)||(badge)||(MozTrap Action badge)||Bugzilla account badge||(QA Testday badge, or MozTrap specific badge)||(QA Testday badge, or MozTrap specific badge)||(QA Testday badge, or MozTrap specific badge)|
in progress for qa
|QA (Automated testing for WebQA)||One and done (?)||Github||. . .|
|QA (for mobile)||Download and install Firefox Nightly for Desktop||Sign-in to 123done.org and myfavoritebeer.org||Create an account on Bugzilla using Persona||Determine if you have an Android device||Download a Nightly version of Fennec||Join a test day|
|Data source||Bugzilla/MozTrap/Github/One and Done|
- See Security pathway
Supporting & volunteering with Mozilla IT is different than other areas. As part of Mozilla IT you will have privileged access to various systems. Contributing here involves a series of elevated levels of trust as you move up in contribution levels.
(Start in Community IT supporting non-Mozilla owned hardware/sites and level up to support Mozilla IT/Systems.)
There are three function areas to volunteer and contribute to Mozilla IT:
- Community IT
Functional Area #1 #2 #3 #4 #5 #6 #7 #8 Community IT TBD TBD TBD TBD TBD TBD TBD TBD Data source
- Mozilla IT/Systems
Functional Area #1 #2 #3 #4 #5 #6 #7 #8 IT/Systems TBD TBD TBD TBD TBD Data source
- Air Mozilla Event Support
Functional Area #1 #2 #3 #4 Event Tech Technical Support Air Mozilla Support Tech Liaison Event Tech Lead
|Creative||Participate in 1 design challenge||Participate in 5 design challenges||Finalist in design challenge||Winner of design challenge||Assigned a design project|
|Recognition||Email/Blog||Badge||Badge||Badge/Shirt||Badge/Invite to team event|
|Creative||Participate in data visualization challenge||Finalist in data visualization challenge||Access to Metrics staging server|
|Add-ons User||Install an add-on||Create an account||Write a review||Create a collection and/or bg theme||Flag user reviews/become a theme reviewer||Join Featured Add-ons Board|
|Add-ons Developer||Create an account||Submit an add-on||Update add-on||Join Featured Add-ons Board||Become reviewer||Reach Reviewer Level 1 Details||Reach Reviewer Level 4+ Details|
|Casual Contributor||Has a fork of Gaia||Has a Bugzilla account||Filed a bug||Filed 10 bugs||Assigned a bug||Made pull request for Gaia bug||Pull request landed with r+||5 pull requests landed|
|Active Contributor||10 pull requests landed||25 pull requests landed||Filed 25 bugs||Filed 50 bugs||1 new feature developed||5 new features developed||reviewed 1 pull request||reviewed 5 pull requests|
|Core Contributor||Received Gaia commit access||50 pull requests landed||100 pull requests landed||10 new features developed||reviewed 25 pull requests||reviewed 50 pull requests||made a module peer||made a module owner|
Other project areas
The conversion points for these project areas are still a work in progress and are not ready yet to be implemented into the Grow Mozilla dashboard.
|Functional Area||Conversion Point #1||Conversion Point #2||Conversion Point #3||Conversion Point #4||Conversion #5||Conversion #6||Conversion #7||Conversion #8||Conversion #9||Conversion #10||Conversion #11|
|Bugmasters||Create a Bugzilla Account||Request more info from bug reporter||Add yourself to Mozillians||Join #bugmasters and introduce yourself||Find and mark a duplicate bug||Move an untriaged bug into a specific component||Add a reduced test case to a bug||Confirm an unconfirmed bug|
|Marketing||Contact us to get involved (contribute page, direct email, etc.)||# of responses sent||Sign up for Marketing Collective||Become a Marketing Collective member|
|L10n||Add name & info to their locale's wiki page as "Localizer-in-training."||Introduction on m.d.l10n newsgroup (or m.d.l10n.new-locales)||Creating a Bugzilla Account||Downloads Firefox Aurora for their locale.||See our background desc. here for more info.|
|Visual Design||Sign up for design mailing list||TBD|
|Developer Documentation (system that has data on this)||Creating an account on MDN (MDN)||Making an edit to an MDN page (MDN)||Making a "significant" addition or update to an MDN page (MDN, based on "size" of edit?)||Participating in #devmo on IRC (IRC bot?)||Subscribing to dev-mdc (mailman)||Posting on dev-mdc (mailman)||Making multiple significant edits to MDN (MDN)|
|User Research||Conduct a cognitive walkthrough||Conduct a usability test||Propose a research project/plan that they are interested in|
|Dev Derby||Visit the Dev Derby||Understand the purpose/goals of the Derby||Like an entry submitted by another user||Create an MDN account||Comment on an entry submitted by another user||Submit an entry||Win a finalist spot||Win third place||Win second place||Win first place||Contribute even after winning first place|