Contribute/Engineering Program Management: Difference between revisions
(Created page with "=Steward= Lawrence Mandel =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 it...") |
No edit summary |
||
| Line 3: | Line 3: | ||
Lawrence Mandel | Lawrence Mandel | ||
= | =Identify Community= | ||
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)? | |||
1. Review the information on the [[Program Management | program management wiki page]] including the active programs and projects and the way in which they're being managed. | 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= | |||
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing? | |||
A: 1. Review the information on the [[Program Management | program management wiki page]] including the active programs and projects and the way in which they're being managed. | |||
2. Identify a program or project that interests you. You can work off of the programs and projects listed on the [[Program Management | program management wiki page]] or suggest a new initiative. | 2. Identify a program or project that interests you. You can work off of the programs and projects listed on the [[Program Management | program management wiki page]] or suggest a new initiative. | ||
| Line 13: | Line 29: | ||
3. Due to the nature of program management the team of program managers is in close contact. Get in touch with the community of program managers to introduce yourself on the [https://lists.mozilla.org/listinfo/dev-planning dev-planning] mailing list or on [irc://irc.mozilla.org/pm irc channel #pm]. | 3. Due to the nature of program management the team of program managers is in close contact. Get in touch with the community of program managers to introduce yourself on the [https://lists.mozilla.org/listinfo/dev-planning dev-planning] mailing list or on [irc://irc.mozilla.org/pm irc channel #pm]. | ||
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. | |||
=Goals= | =Establish Goals and Metrics= | ||
The program management team is working to engage the community in the management of various Firefox initiatives. This is a great opportunity for community members to: | Q: What goals does your team have for bringing in new contributors and how can you measure if you are successful? | ||
A: The program management team is working to engage the community in the management of various Firefox initiatives. This is a great opportunity for community members to: | |||
* understand the overall Firefox project | * understand the overall Firefox project | ||
* get involved with senior leadership of the Firefox project | * get involved with senior leadership of the Firefox project | ||
* broaden your skill set - program management requires skills to bridge the gap between the technical and business sides of a project | * broaden your skill set - program management requires skills to bridge the gap between the technical and business sides of a project | ||
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 18:53, 2 December 2011
Steward
Lawrence Mandel
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: 1. Review the information on the program management wiki page including the active programs and projects and the way in which they're being managed.
2. Identify a program or project that interests you. You can work off of the programs and projects listed on the program management wiki page or suggest a new initiative.
3. Due to the nature of program management the team of program managers is in close contact. Get in touch with the community of program managers to introduce yourself on the dev-planning mailing list or on irc channel #pm.
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: The program management team is working to engage the community in the management of various Firefox initiatives. This is a great opportunity for community members to:
- understand the overall Firefox project
- get involved with senior leadership of the Firefox project
- broaden your skill set - program management requires skills to bridge the gap between the technical and business sides of a project
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.