Confirmed users
2,473
edits
Contribute/Engineering Program Management: Difference between revisions
Contribute/Engineering Program Management (view source)
Revision as of 17:26, 24 July 2012
, 24 July 2012→Identify Community
| (4 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)? | Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)? | ||
A: Martin Best (mbest), Erin Lancaster (elancaster), [https://mozillians.org/en-US/u/8efea2a088 Lawrence Mandel] (lmandel), Sheila Mooney (smooney) | A: [https://mozillians.org/en-US/dietrich Dietrich Ayala] (dietrich), Martin Best (mbest), Erin Lancaster (elancaster), [https://mozillians.org/en-US/u/8efea2a088 Lawrence Mandel] (lmandel), Sheila Mooney (smooney), Michael Treese (mtreese) | ||
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. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up. | 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. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up. | ||
=Define Contribution Opportunities= | =Define Contribution Opportunities= | ||
| Line 21: | Line 21: | ||
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: | ||
# Sign up for [http://bugzilla.mozilla.org Bugzilla]. We do a lot of work in here. | |||
# 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. | |||
# 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. | |||
# 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]. | |||
=Establish Goals and Metrics= | =Establish Goals and Metrics= | ||
| Line 37: | Line 35: | ||
* 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 | ||
* define project management process at Mozilla and create supporting tools | |||
Our goal is to have enough hands to manage all of the many moving pieces of Firefox. This is of course a high level goal that we can refine as a team as we grow. | |||