Contribute/Services: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Steward= Ally Naaktgeboren =Identify Community= Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)? A: Suggestion: Use the [http...")
 
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{outdated}}
[[Category:Contribute]]
[[Category:Services]]
=Steward=
=Steward=


Line 7: Line 11:
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. Communication exists through #sync & the services-dev@mozilla.com mailing list.
 
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.


=Define Contribution Opportunities=
=Define Contribution Opportunities=
Line 15: Line 17:
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: 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.
 
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 24: Line 24:


A:
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.
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=


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:
 
* Goal Q1:
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.
** goal: accquiring a single contributor
 
*** bonus points for a non sync contributor
=Notes=
** retaining the 1(very recent) contributor we havce
 
*** bonus points if he gets L2 access
Luis Villa has written a paper on this that may have helpful ideas and suggestions.
*** bonus points for others we happen to acquire
 
* getting the house in order/which projects are currently in a state to accept contribution?
* [http://www.ifosslr.org/ifosslr/article/download/34/59 Lawyers in the Bazaar: Challenges and Opportunities for Open Source Legal Communities]
** 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

Latest revision as of 21:09, 22 September 2014

Ambox outdated.png THIS PAGE MAY BE OUTDATED
This article is in parts, or in its entirety, outdated. Hence, the information presented on this page may be incorrect, and should be treated with due caution until this flag has been lifted. Help by editing the article, or discuss its contents on the talk page.

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
Retrieved from "https://wiki.mozilla.org/index.php?title=Contribute/Services&oldid=1017145"