Contribute/Conversion points

From MozillaWiki
Jump to navigation Jump to search

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.

Contribution Funnel

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.

Funnel mockup1.png

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.

Funnel mockup2.png

Activity Levels

Activity levels.jpg

  • (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

Contribution 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: As someone passes from casual to active contributor, we should look at way to send out automated invitation to the phonebook.

Coding

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
Data source Bugzilla Bugzilla Bugzilla Bugzilla Hg LDAP Bugzilla Bugzilla LDAP Hg+Pushlog Hg+Pushlog Bugzilla Despot

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 Conversion Point #1 Conversion Point #2 Conversion Point #3 Conversion Point #4 Conversion Point #5
Webdev Creating Bugzilla account Submitting Github pull request Have changes pushed to production Submitting 3 Github pull requests Access to commit to trunk
Data source Bugzilla Github Github Github Github

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
QA Creating a Bugzilla Account Find an engaging project Confirming an unconfirmed bug Verifying fixed bugs File a bug Finding regression ranges for bugs with mozregression Associating crashes in Socorro with bugs Bug triage
Marketing Contact us to get involved (contribute page, direct email, etc.) # of real responses Sign up for Marketing Collective Become a Marketing Collective member
L10n TBD
Addons Create AMO account Install an add-on/Write a review Create a collection Moderate user reviews Create an add-on Become a reviewer/Help review add-ons
Visual Design Sign up for design mailing list TBD
Student Reps Sign up for Student Reps list Host an event Become a Mozilla Rep
Developer Documentation Creating an account on MDN Making an edit to an MDN page Making a "significant" addition or update to an MDN page Participating in #devmo on IRC Subscribing to dev-mdc Posting on dev-mdc Making multiple significant edits to MDN
Accessibility TBD
Systems Administration 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