From MozillaWiki
Jump to: navigation, search


Dan Mills and Christian Heilmann

Identify Community

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

A: Informally have been tracking people on Identity forum. Ask people on existing Identity forum to sign up on Mozillians database and use identity tag.

Suggestion: Use the 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 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

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


  • developers (divides into people working on browserid itself and those implementing it -- same overall skillset but level of experience differs) -- both involve web technologies for instance but level is different)
    • set of bugs available in github issue tracker and assana (sp?) but not in bugzilla
    • campaign ideas: bounty for plug-ins, scoreboard for sign-ups through implemented site, etc.
  • evangelists to spread the word (christian to work with evangeslists on slides, materials, demos, etc, for instance christian's grab bag)
  • localizers (localize browserid itself and docs for it)

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

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


  • developers -- github issues page with starter bugs and github docs and readmes, bug bounty, talking to us in #identity (needed: one page to tie it together)
  • evangelist -- remo and find people who have already done this in an unplanned fashion by asking people to sign up to mozillians directory on identity list -- christian can then more easily find them while traveling.
  • localizers -- reconnect after browserid is localizable.

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

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: how many sites are using browserid, how many plug-ins are created by community, number of talks given, how many new developers are helping out on bugs, surveys about how people found out about it

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.