Contribute/Accessibility: Difference between revisions
DavidBolter (talk | contribs) (Created page with "=Steward= David Bolter =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?...") |
No edit summary |
||
| Line 3: | Line 3: | ||
David Bolter | David Bolter | ||
= | =Identify Community= | ||
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)? | |||
A: | |||
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. | |||
=Define Contribution Opportunities= | |||
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities? | |||
A: | |||
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. | |||
= | =Map Contribution Paths= | ||
What | Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing? | ||
A: | |||
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: | |||
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. | |||
Revision as of 22:25, 7 November 2011
Steward
David Bolter
Identify Community
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?
A:
Suggestion: Use the 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.
Define Contribution Opportunities
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
A:
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.
Map Contribution Paths
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?
A:
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:
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.