Contribute/Security Engineering
|
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. |
Contents
Steward
Curtis Koenig
Identify Community
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?
A:
- Lucas Adamski
- Al Billings
- Yvan Boily
- David Chan
- Michael Coates
- Guillaume Destuynder
- Christoph Diehl
- Raymond Forbes
- Mark Goodwin
- Chris Hofmann
- Christian Holler
- David Keeler
- Curtis Koenig
- Gary Kwong
- Ian Melvin
- Adam Muntner
- Eric Parker
- Jesse Ruderman
- Sid Stamm
- Joe Stevensen
- Brandon Sterne
- Dan Veditz
- Tanvi Vyas
Suggestion: Use the 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. 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?
A: There are currently 2 ways to contribute:
- Interested parties can join in our security review & discussions by monitoring the Security Review Calendary and joining in as your interest allows. All information for joining our meetings is available with each instance.
- Find and report security bugs.
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?
A:
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:
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.
