: New feature! MozillaWiki is now mobile-friendly. Visit from a mobile device to see new mobile theme + try editing. Release details.

Contribute/Conversion points

From MozillaWiki
Jump to: navigation, search

This page details the Conversion points of Contribution Pathways across various projects of Mozilla. The primary reason for detailing those is the articulation of pathways, and the secondary reason is for those conversion points to be used as aggregation scenarios to produce metrics for different projects.

Conversion Points

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.png
Active Contributor
Using the lowest active contributor conversion point for each area we are aggregating and producing counts for our Contributors Dashboard

Coding

Because of the number of conversion points involved, I've organized these into tiers of contributions that are of roughly equal value and difficulty. They correspond to the tiers outlined in the [pathways document here.] - mhoye


Casual Contributor Conversion points. Metrics Rewards & Recognition Next Steps
Installing Nightly mzl.la, download count Thanks on Nightly page. Get a Bugzilla account, build Firefox.
Creating Bugzilla account Bugzilla (feeds Baloo) A badge (automatic) File a bug, reproduce a bug.
Filing a bug Bugzilla Thanks, maybe automated badge-awarding? Contributor is invited to create a Mozillians acc't. Creating a test case, triaging a bug.
Creating a test case HG (?) A badge (manual) Build Firefox, create a patch.
Creating a Mozillians Account Mozillians.org None Follow a Mozillians group (Themed? Regional?), look at the Reps program.
Active Contributor Conversion Point Metrics Rewards & Recognition Next Steps
Submitting a patch / Filing a pull request Bugzilla / Github Message of thanks. Invite contributor to sign up for Mozillians. Working through patch review/resubmit process.
Having patches r+’ed and merged Mercurial (script something for Github?) Badge, Name in about:credits, callout in release notes for first patch. Recognition at various contribution intervals - 1, 3, 5, 10, 25, 50, 100... Apply for try-server access
Gain try-server (Commit Level 1) access Bugzilla Badge on Mozillians (For access? For first all-green push?) Direct contributor to a next patch, offer a mentored bug that appears to be a good fit.
Core Contributors Conversion Points Metrics Rewards & Recognition Next Steps
Consistent Tier 1/2 participation across several (3, 4+?) releases. Mercurial, other Badge? Lotta badges getting thrown around here. People who make it here for a few releases and then disappear need to be followed up through separate channels.
Gaining Level 2 commit access Mercurial? LDAP? Everything gets a badge, I guess, but we should send a shirt at this point. More of the same.
Mentoring a new contributor through the contribution process. Bugzilla, maybe? Need an answer for this one. Badge on Mozillians, mention in “mentors” section in release notes. The mentoring doc. Do we need a Mentors dashboard?
Reviewing patches / pull requests Bugzilla / Github First reviewed patch merged should be worth something interesting. Swag?


Firefox OS

Contributor #1 #2 #3 #4 #5 #6 #7 #8
Casual Contributor Has a fork of Gaia Has a Bugzilla account Filed a bug Filed 10 bugs Get a bug assigned to him/her 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
Recognition  ?  ?  ?  ?  ?  ?  ?  ?
2013 Conversions*  ?  ?  ?  ?  ?  ?  ?  ?

Support

Onboarding conversion

Functional Area Conversion point #1 Conversion point #2
Support Creating SUMO account Engaging in SUMO activities
Data source SUMO SUMO


Activity levels

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
Data source SUMO SUMO SUMO SUMO

Webdev

Functional Area #1 #2 #3 #4 #5 #6 #7 #8
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
Data source Github Github Github Github Github Github Github Bugzilla
Recognition Badge Badge & ? Badge & Invitation to Mozillians.org Badge & ? Badge & ? Badge & ? Badge & ?  ?
2012 Conversions*  ? (hundreds-thousands)  ? (hundreds) 137 38 20 9 0  ?

QA

Onboarding pathways

Functional Area #1 #2 #3 #4 #5 #6 #7 #8
QA (One and Done) Create a One and Done account Finish 3 cases in One and Done per quarter Finish 10 cases in One and Done per quarter. Finish 20 cases in One and Done per quarter Finish 30 cases in One and Done per quarter Creating cases in One and Done Organizing test days TBD
Data source One and Done new account One and Done finished tasks One and Done finished tasks One and Done finished tasks One and Done finished tasks One and Done task owner TBD TBD
Recognition TBD Badge TBD TBD TBD TBD TBD TBD TBD


Functional Area #1 #2 #3 #4 #5 #6 #7 #8
QA (MozTrap/manual testing) Create a MozTrap account Pass or fail 10 cases in MozTrap per quarter Pass or fail 30 cases in MozTrap per quarter. Pass or fail 50 cases in MozTrap per quarter. Pass or fail 100 cases in MozTrap per quarter. Create a test run in MozTrap (per quarter) TBD TBD
Data source MozTrap new account MozTrap case pass/fails MozTrap case pass/fails MozTrap case pass/fails TBD TBD TBD TBD
Recognition Badge TBD Badge TBD TBD TBD TBD TBD TBD TBD


Functional Area #1 #2 #3 #4 #5 #6 #7 #8
QA (WebQA Pull requests) Comment or submit a PR on a Web QA repo in github in the last month More than one commend or PR submission in the last month. Merged pull request in a Web QA repo in github in the last month Three merged pull requests in a Web QA repo in the last month. n/a TBD TBD TBD
Data source Github Github Github Github TBD TBD TBD TBD
Recognition Badge TBD Badge Badge TBD TBD TBD TBD


Functional Area #1 #2 #3 #4 #5 #6 #7 #8
QA (Bug triage - take 2) Create an account on Bugzilla using Persona Help triage 3 bugs per quarter in bugzilla.mozilla.org Help triage 10 bugs per quarter in BMO Help triage 25 bugs per quarter in BMO Help triage 40 bugs per quarter in BMO TBD TBD TBD
Data source Bugzilla new account Bugzilla status, product, component, bugs commented on (not # of comments, but # of bugs in which you've left at least one comment) Bugzilla status, product, component, bugs commented on Bugzilla status, product, component, bugs commented on Bugzilla status, product, component, bugs commented on TBD TBD TBD
Recognition Bugzilla account badge Bugzilla action badge (badge), considered for canconfirm permissions on BMO (badge) (badge) TBD TBD TBD

Possibly obsolete pathways - not for Baloo project

Functional Area #1 #2 #3 #4 #5 #6 #7 #8
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)


Functional Area #1 #2 #3 #4 #5 #6 #7 #8
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

Functional Area #1 #2 #3 #4 #5 #6 #7 #8
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
Recognition

Security

Mozilla IT

[DRAFT]

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:

  1. Community IT
    Functional Area #1 #2 #3 #4 #5 #6 #7 #8
    Community IT TBD TBD TBD TBD TBD TBD TBD TBD
    Data source
  2. Mozilla IT/Systems
    Functional Area #1 #2 #3 #4 #5 #6 #7 #8
    IT/Systems TBD TBD TBD TBD TBD
    Data source
  3. Air Mozilla Event Support
    Functional Area #1 #2 #3 #4
    Event Tech Technical Support Air Mozilla Support Tech Liaison Event Tech Lead

Creative

Functional Area #1 #2 #3 #4 #5
Creative Participate in 1 design challenge Participate in 5 design challenges Finalist in design challenge Winner of design challenge Assigned a design project
Data source Flickr Flickr Bugzilla
Recognition Email/Blog Badge Badge Badge/Shirt Badge/Invite to team event

Metrics

Functional Area #1 #2 #3
Creative Participate in data visualization challenge Finalist in data visualization challenge Access to Metrics staging server
Data source Github Github
Recognition

Reps

Casual Contributor Active Contributor Core Contributor
Action One activity within 8 weeks period One activity within 4 weeks period Four activities within 4 weeks period
Data source reps.mozilla.org reps.mozilla.org reps.mozilla.org
Recognition

AMO (addons.mozilla.org)

Functional Area #1 #2 #3 #4 #5 #6 #7
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

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)
Accessibility TBD
User Research Conduct a cognitive walkthrough Conduct a usability test Propose a research project/plan that they are interested in
Thunderbird TBD
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


Mozilla Foundation (MoFo)

Webmaker Total

Active Contributor Conversion Point Metrics Datasource Rewards & Recognition Next Steps
Qualifying as a Webmaker Mentor or Super-Mentor Ad-hoc logger, via Badgekit API tbc tbc
Hosting or Volunteering at a Webmaker Event Webmaker Events Database & Reps Events Database Tagged as Webmaker tbc tbc
Translating Webmaker Tools Transifex tbc tbc
Ad-hoc Contribution including
  • Presenting on community calls
  • Face-to-face user testing
  • Informal QA
  • Building Appmaker Components
  • Building on the MakeAPI
Ad-hoc Contribution Logger tbc tbc
Code Contribution Merged Github tbc tbc
Filing a Bug Bugzilla tbc tbc
Submitting Web Literacy Resources Webmaker DB tbc tbc
Creating Teach Kits (Open Educational Resources) TBC - not tracked yet tbc tbc
Creating 'high-value' starter makes and appmaker templates TBC - not tracked yet tbc tbc

Webmaker Tools Team

This view is a subset of Webmaker Total for team specific goal tracking.

Active Contributor Conversion Point Metrics Datasource Rewards & Recognition Next Steps
Code Contribution Merged Github tbc tbc
Filing Bugs Github & Bugzilla tbc tbc

Appmaker

This view is a subset of Webmaker Total for team specific goal tracking.

Active Contributor Conversion Point Metrics Datasource Rewards & Recognition Next Steps
Code Contribution Merged Github tbc tbc
Filing Bugs Github tbc tbc
Ad-hoc Contribution including
  • Presenting on community calls
  • Face-to-face user testing
  • Informal QA
  • Building Appmaker Components
Ad-hoc Contribution Logger tbc tbc

Hive

This view is a subset of Webmaker Total for team specific goal tracking.

Active Contributor Conversion Point Metrics Datasource Rewards & Recognition Next Steps
Qualifying as a Hive Community Member Ad-hoc logger, via Badgekit API tbc tbc
Ad-hoc Contribution including
  • Presenting on community calls
  • Face-to-face user testing
  • Informal QA
  • Building Appmaker Components
  • Building on the MakeAPI
Ad-hoc Contribution Logger tbc tbc

Mozilla Science Lab

Active Contributor Conversion Point Metrics Datasource Rewards & Recognition Next Steps
Teaching or Volunteering at a bootcamp Ad-hoc logger via Software Carpentry Admin DB tbc tbc
Contributing lesson material datasource tbc tbc
Ad-hoc Contribution including
  • Presenting on community calls
  • Peer-reviewing lesson material
  • Testing/QA on prototypes
  • Guest blogging on Science Lab site
Ad-hoc Contribution Logger tbc tbc
Code Contribution Merged Github tbc tbc
Filing Bugs Bugzilla tbc tbc

Knight-Mozilla OpenNews

Active Contributor Conversion Point Metrics Datasource Rewards & Recognition Next Steps
Open News Fellows  ? tbc tbc
Writing for Source Source DB tbc tbc
Participation in OpenNews community projects Source DB tbc tbc
Ad-hoc Contribution including
  • Presenting on community calls
  • Organizing local events
  • Informal QA
Ad-hoc Contribution Logger tbc tbc
Code Github tbc tbc

MozFest

Active Contributor Conversion Point Metrics Datasource Rewards & Recognition Next Steps
Volunteer BSD tbc tbc
Host a session BSD tbc tbc
Participate in a session BSD tbc tbc

Advocacy

TBC

Metrics

TBC