Contribute/Labs: Difference between revisions

 
(5 intermediate revisions by 2 users not shown)
Line 12: Line 12:


At this point, we are still in the process of rethinking what Labs is like, and until we do so, it's hard to know how we're going to grow contributors, although we know we need to.
At this point, we are still in the process of rethinking what Labs is like, and until we do so, it's hard to know how we're going to grow contributors, although we know we need to.
We very much want to grow Labs contributors, but it'll have to wait until early Q1.


=Define Contribution Opportunities=
=Define Contribution Opportunities=
Line 17: Line 19:
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: No (see above)
 
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=
=Map Contribution Paths=
Line 25: Line 25:
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: Not yet as a rule, although there are probably exceptions.
 
To expand on the answer, PDF.js is one such exception for code contributors: https://github.com/mozilla/pdf.js  - the steps are outlined clearly on github. However, until the Moz Labs website is back online with good search & navigation, it's difficult to find out about this project unless you know where to look.
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=
=Establish Goals and Metrics=
Line 33: Line 32:
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?
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: Not yet, but some thoughts:


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.
* for code projects, use code metrics (bug reports, patches, reviews, commits, etc.)
* for design projects, use design metrics (participants in design reviews/charettes, original submissions, etc.)
* for partnership projects, number of partners actively engaged in prototyping

Latest revision as of 22:35, 30 April 2012

Steward

Havi Hoffman and David Ascher

Identify Community

Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?

A: No.

Less flippantly, Labs has been under massive change this year with many people shifting from an exploration role to a product development role w/ the Identity and Apps initiatives. This has impacted both paid staff and volunteers.

At this point, we are still in the process of rethinking what Labs is like, and until we do so, it's hard to know how we're going to grow contributors, although we know we need to.

We very much want to grow Labs contributors, but it'll have to wait until early Q1.

Define Contribution Opportunities

Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?

A: No (see above)

Map Contribution Paths

Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?

A: Not yet as a rule, although there are probably exceptions. To expand on the answer, PDF.js is one such exception for code contributors: https://github.com/mozilla/pdf.js - the steps are outlined clearly on github. However, until the Moz Labs website is back online with good search & navigation, it's difficult to find out about this project unless you know where to look.

Establish Goals and Metrics

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: Not yet, but some thoughts:

  • for code projects, use code metrics (bug reports, patches, reviews, commits, etc.)
  • for design projects, use design metrics (participants in design reviews/charettes, original submissions, etc.)
  • for partnership projects, number of partners actively engaged in prototyping