Contribute/Coding: Difference between revisions
Jump to navigation
Jump to search
(→Goals) |
(→Goals) |
||
| Line 30: | Line 30: | ||
Proposed goal: Create and maintain a curated list of 50 mentored bugs that can be handed out to promising new contributors. | 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? | Sub-proposal: Ensure some sort of distribution across lots of components? | ||
Revision as of 02:46, 4 October 2011
Steward
Dietrich Ayala, Kyle Huey, Brian Bondy and Josh Matthews
Contribution Paths
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?
1. Submit
2. Verification
3. Triage
4. Assignment
5. Patch Coding
6. Code Review
7. Security
8. Patch Release
9. Ticket Closed
Goals
What goals does your team have for bringing in new contributors to your project area?
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?
Metrics
What data is available to measure if we're meeting your goals?