Confirmed users, Bureaucrats and Sysops emeriti
421
edits
Contribute/Coding/Pathways: Difference between revisions
→Tier 2 - Active Contributors
| Line 53: | Line 53: | ||
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. | 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. | ||
Active Contributors may enjoy: | |||
* Submitting a patch / Filing a pull request | * Submitting a patch / Filing a pull request | ||
** Metrics: Bugzilla / Github | ** Metrics: Bugzilla / Github | ||
** Rewards/recognition: Message of thanks. | ** Rewards/recognition: Message of thanks. | ||
** Related initiatives: | ** Related initiatives: (Github <-> Baloo?) | ||
** 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. | ** 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, if they have not yet done so. | ||
** Next steps: | ** Next steps: Working through patch review/resubmit process. | ||
* 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. Recognition at various contribution intervals - 1, 3, 5, 10, 25, 50, 100... | ** Rewards/recognition: Badge, 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: ReviewBoard integration with Baloo is going to be important. | ** Related initiatives: ReviewBoard integration with Baloo is going to be important. | ||
** Followup: When a patch is r+’ed, contributors should be guided towards their next bug. | ** Followup: When a patch is r+’ed, contributors should be guided towards their next bug. | ||
** Next steps: | ** Next steps: Apply for try-server access | ||
* | * Gain try-server (Commit Level 1) access | ||
** Metrics: Bugzilla | ** Metrics: Bugzilla | ||
** Rewards/recognition: Badge on Mozillians (For access? For first all-green push?) | ** Rewards/recognition: Badge on Mozillians (For access? For first all-green push?) | ||
** Related initiatives: Eventual ReviewBoard integration. | ** Related initiatives: Eventual ReviewBoard integration. | ||
** Followup: | ** Followup: We should figure out how to celebrate somebody's first all-green test run. | ||
** Next steps: | ** Next steps: Direct contributor to a next patch, offer a mentored bug that appears to be a good fit. | ||
=== Tier 3 - Core Contributors === | === Tier 3 - Core Contributors === | ||