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