Contribute/Automation: Difference between revisions
| Line 27: | Line 27: | ||
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing? | Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing? | ||
A: | A: Yes, we are marking bugs with [https://bugzilla.mozilla.org/buglist.cgi?list_id=1802521&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=goodfirstbug&product=Testing "goodfirstbug"] and each of those bugs has a mentor. You can find that mentor on IRC for more details. We also have a [https://wiki.mozilla.org/Auto-tools/New_Contributor new contributor] page that details much of what kinds of setup you'll need to be productive on the team and understand the lingo we use. Most importantly, if you have questions, just ask. | ||
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. | 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. | ||
Revision as of 21:01, 30 November 2011
Steward
Clint Talbert, Lukas Blakk and Henrik Skupin
Note: There are different automation teams at Mozilla (Build Automation, Tools and Automation, QA Automation) and the goal is to provide a simple entry point for people interested in automation and then provide more information to people about the full range of contribution options after they get some initial experience with Mozilla.
Identify Community
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?
The Automation and Tools community goes by the moniker a-team. You can check us out on mozillians
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: The A-Team needs people that work on javascript, python, and web design to help out with a bunch of projects. You can see our areas where we could use help and our current and past projects to see what types of things we do.
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: Yes, we are marking bugs with "goodfirstbug" and each of those bugs has a mentor. You can find that mentor on IRC for more details. We also have a new contributor page that details much of what kinds of setup you'll need to be productive on the team and understand the lingo we use. Most importantly, if you have questions, just ask.
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.