Confirmed users, Bureaucrats and Sysops emeriti
421
edits
Contribute/Coding/Pathways: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
It is broadly based on the [https://wiki.mozilla.org/Contribute/Pathways Pathways model] adopted by the Communiy Building Team. Engagement points that feed into to the Coding pathway are [https://wiki.mozilla.org/Contribute/Coding/Engagement listed on the Engagement page]. | It is broadly based on the [https://wiki.mozilla.org/Contribute/Pathways Pathways model] adopted by the Communiy Building Team. Engagement points that feed into to the Coding pathway are [https://wiki.mozilla.org/Contribute/Coding/Engagement listed on the Engagement page]. | ||
As of early 2014, Mozilla's biggest challenges around community growth revolve around accessibility and retention; the two biggest dials we can turn to drive contribution rates are to make it easier for new participants to contribute and rewarding for them to | As of early 2014, Mozilla's biggest challenges around community growth revolve around accessibility and retention; the two biggest dials we can turn to drive contribution rates are to make it easier for new participants to contribute and rewarding for them to continue. | ||
= Contribution Tiers = | = Contribution Tiers = | ||
| Line 15: | Line 13: | ||
These are the foot-in-the-door starting points and entry-level contributions that are the bread and butter of community contribution. They don't (and should not) present a high bar to participation, and be amenable to anonymous contribution where possible. | These are the foot-in-the-door starting points and entry-level contributions that are the bread and butter of community contribution. They don't (and should not) present a high bar to participation, and be amenable to anonymous contribution where possible. | ||
Tier 1 contributions include: | |||
* Installing Nightly | * Installing Nightly | ||
| Line 41: | Line 40: | ||
** Rewards/recognition: A badge (manual) | ** Rewards/recognition: A badge (manual) | ||
** Related initiatives: | ** Related initiatives: | ||
** Followup: This may count as a contribution - up to the discretion of the filer - towards adding that contributor to | ** Followup: This may count as a contribution - up to the discretion of the filer - towards adding that contributor to Mozilla’s list of contributors. | ||
** Next steps: | ** Next steps: | ||
| Line 52: | Line 51: | ||
=== Tier 2 === | === Tier 2 === | ||
This is the target tier for contributor engagement; we know that the dropout rate between third and fourth contributions is dramatically lower than between first and second, so fostering contributors at this level - a process as simple as prompt replies to questions and basic acknowledgement of their contributions - is essential. | |||
* Submitting a patch / Filing a pull request | * Submitting a patch / Filing a pull request | ||
| Line 60: | Line 61: | ||
** Next steps: | ** Next steps: | ||
* Having | * Having patches r+’ed and merged | ||
** Metrics: Mercurial (script something for Github?) | ** Metrics: Mercurial (script something for Github?) | ||
** Rewards/recognition: Name in about:credits, callout in release notes for first patch. | ** Rewards/recognition: Name in about:credits, callout in release notes for first patch. Recognition at various contribution intervals - 1, 3, 5, 10, 25, 50, 100... | ||
** Related initiatives: | ** Related initiatives: ReviewBoard integration with Baloo is going to be important. | ||
** Followup: When a patch is r+’ed, | ** Followup: When a patch is r+’ed, contributors should be guided towards their next bug. | ||
** Next steps: | ** Next steps: | ||
| Line 76: | Line 77: | ||
=== Tier 3 === | === Tier 3 === | ||
These are consistent | These are consistent contributors | ||
* Consistent Tier 1 participation across (3+?) consecutive releases. | |||
** Metrics: HG | |||
** Rewards/recognition: Badge? | |||
** Related initiatives: | |||
** Followup: | |||
** Next steps: | |||
* Gaining Level 1/2 commit access | * Gaining Level 1/2 commit access | ||
| Line 114: | Line 122: | ||
* Becoming a module owner or peer | * Becoming a module owner or peer | ||
** Metrics: Despot (LDAP?) | ** Metrics: Despot (LDAP?) | ||
= Gardening And Routine Maintenance = | |||
To support the tiered engagement approach and measure its ongoing success, Mike Hoye will be pursuing the following goals: | |||
* Maintain a list of minimum of 40 good first bugs with active mentors at all times. | |||
* Maintain a list minimum of 30 good next bugs with active mentors at all times. | |||
* Identify 10 "diamond" work items each two-week iteration with willing mentors. | |||
* Verify that all the above meet the criteria laid out in the [https://wiki.mozilla.org/Contribute/Coding/Mentoring Mentoring guidelines] | |||
* | |||