Confirmed users, Bureaucrats and Sysops emeriti
421
edits
Contribute/Conversion points: Difference between revisions
Jump to navigation
Jump to search
→Coding
(→Coding) |
|||
| Line 14: | Line 14: | ||
''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.'' | ''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.'' | ||
{| border="1" | {| border="1" | ||
! | ! Conversion point !! Metrics !! Rewards & Recognition !! Next Steps | ||
|- | |- | ||
| style="background:orange;" | Tier 1 - First Contributions | |||
| style="background: | |||
|- | |- | ||
| | | style="background:yellow;" | Installing Nightly | ||
| mzl.la, download count | |||
| Thanks on Nightly page. | |||
| Get a Bugzilla account, build Firefox. | |||
|- | |||
| style="background:yellow;" |Creating Bugzilla account | |||
| Bugzilla (feeds Baloo) | |||
| A badge (automatic) | |||
| File a bug, reproduce a bug. | |||
|- | |||
| style="background:yellow;" |Filing a bug | |||
| Bugzilla | | Bugzilla | ||
| Thanks, maybe automated badge-awarding? Contributor is invited to create a Mozillians acc't. | |||
| Creating a test case, triaging a bug. | |||
|- | |||
| style="background:yellow;" |Creating a test case | |||
| HG (?) | |||
| A badge (manual) | |||
| Build Firefox, create a patch. | |||
|- | |||
| style="background:yellow;" |Creating a Mozillians Account | |||
| Mozillians.org | |||
| None | |||
| Follow a Mozillians group (Themed? Regional?), look at the Reps program. | |||
|- | |||
| style="background:orange;" | Tier 2 - Active Contributions | |||
|- | |||
| style="background:yellow;" |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. | |||
|- | |||
| style="background:yellow;" |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 | |||
|- | |||
| style="background:yellow;" | Gain try-server (Commit Level 1) access | |||
| Bugzilla | | 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. | ||
|- | |- | ||
| | | style="background:green;" | Tier 3 - Core Contributors | ||
| | |- | ||
| | | style="background:yellow;" |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. | ||
| | |- | ||
| | | style="background:yellow;" |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. | ||
| | |- | ||
| | | style="background:yellow;" | 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. [[Contribute/Coding/Mentoring#Good_Mentored_Bugs|The mentoring doc]]. | |||
| Do we need a Mentors dashboard? | |||
|- | |||
| style="background:yellow;" | Reviewing patches / pull requests | |||
| Bugzilla / Github | |||
| First reviewed patch merged should be worth something interesting. Swag? | |||
|} | |} | ||
===Firefox OS=== | ===Firefox OS=== | ||