Contribute/Services

Steward

Ally Naaktgeboren

Identify Community

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

A: Yes. Communication exists through #sync & the services-dev@mozilla.com mailing list.

Define Contribution Opportunities

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

A: They talk to the steward, usually in #sync, who pairs them with bugs based on their interests, time expectations, abilities, and the team's needs. The needs of services vary highly.

Map Contribution Paths

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

A: The full set of steps depend on what you want to work on. Firefox desktop UI is very different from Notifications for example. In general, talk to the steward first, get a bugzilla account, and the steward will mentor you through finding a starting bug and a mentor for it.

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:

• Goal Q1:
  • goal: accquiring a single contributor
    • bonus points for a non sync contributor
• retaining the 1(very recent) contributor we havce
  • bonus points if he gets L2 access
  • bonus points for others we happen to acquire
• getting the house in order/which projects are currently in a state to accept contribution?
  • desktop sync
  • native android sync
  • Sagrada
  • Sui
  • BiPostal
  • notifications
  • and this list is probably already stale
  • BrowserID
• Metrics we wish we had
  • frequency of commits on their behalf (unsurprisingly we have no contributors who can land their own code at this time)
  • number of hours represented by those commits
  • happiness of our contributors
  • health of staff/contributor relations