Contribute/Coding/Pathways: Difference between revisions

Contribute/Coding/Pathways (view source)

Revision as of 15:36, 28 March 2014

529 bytes added , 28 March 2014

no edit summary

Mhoye

Confirmed users, Bureaucrats and Sysops emeriti

421

edits

@@ Line 9: / Line 9: @@
 === The Foot In The Door ===
-This is the very
+These are the starting points, perhaps obviously. While they are not a particularly high bar to achieve, they are the first place that Mozilla can put a (proverbial) name to a face.
 * Installing Nightly
@@ Line 29: / Line 29: @@
 * Filing a bug
 ** Metrics: Bugzilla
-** Rewards/recognition: Non-spurius bugs
+** Rewards/recognition: Thanks. I
 ** Related initiatives: Automated badge-awarding and metrics integrated into [https://wiki.mozilla.org/Baloo Baloo] gives us lots of
-** Followup:
+** Followup: Contributor is invited to create a Mozillians acc't. When a bug or its dupe is resolved fixed, first-time contributors should be receive a note thanking them for their contribution.
 ** Next steps:
@@ Line 58: / Line 58: @@
 * Having (1,3,5,10) patche(s) r+’ed and merged
-** Metrics: Mercurial
+** Metrics: Mercurial (script something for Github?)
 ** Rewards/recognition: Name in about:credits, callout in release notes for first patch.
-** Related initiatives:
+** Related initiatives: Eventual ReviewBoard integration
 ** Followup: When a patch is r+’ed, a first-time contributor should be guided towards their next bug.
 ** Next steps:
@@ Line 68: / Line 68: @@
-Mentoring a new contributor through the contribution process.
+* Gaining Level 1 commit access
-Metrics: Unclear
+** Metrics: HG
-Rewards/recognition: Badge on Mozillians, mention in “mentors” section in release notes.
+** Rewards/recognition: Badge?
-Related initiatives:
+** Related initiatives:
-Followup:
+** Followup:
-Next steps:
+** Next steps:
+* Mentoring a new contributor through the contribution process.
+** Metrics: Unclear
+** Rewards/recognition: Badge on Mozillians, mention in “mentors” section in release notes.
+** Related initiatives:
+** Followup:
+** Next steps:
+* Providing patch feedback / Conducting reviews
+** Metrics:
+** Rewards/recognition:
+** Related initiatives:
+** Followup:
+** Next steps:
+* Gaining Level 3 commit access
+** Metrics:
+** Rewards/recognition:
+** Related initiatives:
+** Followup:
+** Next steps:
-Gaining Level 1 commit access
+* Checking in your own code to repo
-Metrics: HG
+** Metrics:
-Rewards/recognition: Badge?
+** Rewards/recognition:
-Related initiatives:
+** Related initiatives:
-Followup:
+** Followup:
-Next steps:
+** Next steps:
-Providing patch feedback / Conducting reviews
+* Pushing someone else's code to repo
-Metrics:
+** Metrics:
-Rewards/recognition:
+** Rewards/recognition:
-Related initiatives:
+** Related initiatives:
-Followup:
+** Followup:
-Next steps:
+** Next steps:
-Gaining Level 3 commit access
+* Mentoring a bug
-Metrics:
+** Metrics:
-Rewards/recognition:
+** Rewards/recognition:
-Related initiatives:
+** Related initiatives:
-Followup:
+** Followup:
-Next steps:
+** Next steps:
-Checking in your own code to repo
+* Becoming a module owner or peer
-Metrics:
+** Metrics:
-Rewards/recognition:
+** Rewards/recognition:
-Related initiatives:
+** Related initiatives:
-Followup:
+** Followup:
-Next steps:
+** Next steps:
-Pushing someone else's code to repo
-Metrics:
-Rewards/recognition:
-Related initiatives:
-Followup:
-Next steps:
-Mentoring a bug
-Metrics:
-Rewards/recognition:
-Related initiatives:
-Followup:
-Next steps:
-Becoming a module owner or peer
-Metrics:
-Rewards/recognition:
-Related initiatives:
-Followup:
-Next steps: