Contribute/Developer Tools: Difference between revisions

m
(Created page with "=Steward= =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...")
 
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Steward=
=Steward=


 
Paul Rouget and Christian Heilmann


=Identify Community=
=Identify Community=
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:
A: Yes. Check this out: https://mozillians.org/en-US/group/237-devtools


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.
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 15: Line 15:
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?


A:
A: http://is.gd/bugs_devtools_with_mentor


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.
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.
Line 29: Line 29:
=Establish Goals and Metrics=
=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?
Q: Can you measure participation or contributors today? If so, what metrics can you track?  What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?


A:
A: number of bug fixed and/or reported


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.
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.
canmove, Confirmed users
7,088

edits