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

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.

What data is available to measure if we're meeting your goals?