Contribute/Coding: Difference between revisions

Contribute/Coding (view source)

Revision as of 22:49, 7 November 2011

1,224 bytes added , 7 November 2011

no edit summary

Davidwboswell

canmove, Confirmed users

7,088

edits

@@ Line 3: / Line 3: @@
 Dietrich Ayala, Kyle Huey, Brian Bondy and Josh Matthews
-=Contribution Paths=
+=Identify Community=
-What are the steps someone can take to get involved in your project and learn enough to be able to start scratching their own itch?
+Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?
-. Submit
+A:
-. Verification
+Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help.  Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag.
-. Triage
+=Define Contribution Opportunities=
-. Assignment
+Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
-. Patch Coding
+A:
-. Code Review
+Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities.  Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.
-. Security
+=Map Contribution Paths=
-. Patch Release
+Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?
-. Ticket Closed
+A:
-=Goals=
+* 1. Submit
-What goals does your team have for bringing in new contributors to your project area?
+* 2. Verification
-Proposed goal: Create and maintain a curated list of 50 mentored bugs that can be handed out to promising new contributors.
+* 3. Triage
-Sub-proposal: Ensure some sort of distribution across lots of components?
+* 4. Assignment
-=Metrics=
+* 5. Patch Coding
-What data is available to measure if we're meeting your goals?
+* 6. Code Review
+* 7. Security
+* 8. Patch Release
+* 9. Ticket Closed
+Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.
+=Establish Goals and Metrics=
+Q: What goals does your team have for bringing in new contributors and how can you measure if you are successful?
+A:
+* Proposed goal: Create and maintain a curated list of 50 mentored bugs that can be handed out to promising new contributors.
+* Sub-proposal: Ensure some sort of distribution across lots of components?
+Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today.  We'll work on implementing dashboards when we know what data we want.
 =Ideas=