Confirmed users, Bureaucrats and Sysops emeriti
421
edits
Contribute/Coding/Pathways: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
=== Tier 1 === | === Tier 1 === | ||
These are | |||
* Filing a bug | * Filing a bug | ||
| Line 34: | Line 36: | ||
** Next steps: | ** Next steps: | ||
* | * Creating a test case | ||
** Metrics: HG (?) | ** Metrics: HG (?) | ||
** Rewards/recognition: A badge (manual) | ** Rewards/recognition: A badge (manual) | ||
| Line 46: | Line 48: | ||
Related initiatives: | Related initiatives: | ||
Followup: The signup process should present users with engineering-relevant groups to sign up for. | Followup: The signup process should present users with engineering-relevant groups to sign up for. | ||
Next steps: | Next steps: | ||
=== Tier 2 === | === Tier 2 === | ||
* Submitting a patch | * Submitting a patch / Filing a pull request | ||
** Metrics: Bugzilla | ** Metrics: Bugzilla / Github | ||
** Rewards/recognition: | ** Rewards/recognition: Message of thanks. | ||
** Related initiatives: | ** Related initiatives: | ||
** Followup: Prompt. As per [https://wiki.mozilla.org/Contribute/Coding/Mentoring#Reviewer_Followup here] we know that prompt review of a patch is strongly correlated to contributor retention. | ** Followup: Prompt. As per [https://wiki.mozilla.org/Contribute/Coding/Mentoring#Reviewer_Followup here] we know that prompt review of a patch is strongly correlated to contributor retention. Invite contributor to sign up for Mozillians. | ||
** Next steps: | ** Next steps: | ||
| Line 64: | Line 66: | ||
** Next steps: | ** Next steps: | ||
* Try server access | |||
** Metrics: Bugzilla | |||
** Rewards/recognition: Badge on Mozillians (For access? For first all-green push?) | |||
** Related initiatives: Eventual ReviewBoard integration. | |||
** Followup: | |||
** Next steps: | |||
== | === Tier 3 === | ||
* Gaining Level 1 commit access | * Gaining Level 1 commit access | ||
| Line 74: | Line 81: | ||
** Followup: | ** Followup: | ||
** Next steps: | ** Next steps: | ||
* Mentoring a new contributor through the contribution process. | * Mentoring a new contributor through the contribution process. | ||
| Line 84: | Line 89: | ||
** Next steps: | ** Next steps: | ||
* Reviewing patches / pull requests | |||
* | ** Metrics: Bugzilla / Github | ||
** Metrics: | ** Rewards/recognition: | ||
** Rewards/recognition: | |||
** Related initiatives: | ** Related initiatives: | ||
** Followup: | ** Followup: | ||
** Next steps: | ** Next steps: | ||
=== High-level contributors === | |||
At this point typical rewards for contributions become a disincentive, and more meaningful | |||
* Gaining Level 3 commit access | * Gaining Level 3 commit access | ||
** Metrics: | ** Metrics: LDAP | ||
* Checking in your own code to repo | * Checking in your own code to repo | ||
** Metrics: | ** Metrics: Mercurial / Github | ||
* Pushing someone else's code to repo | * Pushing someone else's code to repo | ||
** Metrics: | ** Metrics: Mercurial / Github | ||
* Becoming a module owner or peer | * Becoming a module owner or peer | ||
** Metrics: | ** Metrics: Despot (LDAP?) | ||