Difference between revisions of "Contribute"
(→Geographic Areas) |
(→Functional Areas) |
||
Line 20: | Line 20: | ||
{| border="1" | {| border="1" | ||
! Area !! Steward | ! Area !! Steward | ||
− | |||
− | |||
− | |||
|- | |- | ||
| [[Stewards/Coding|Coding]] | | [[Stewards/Coding|Coding]] | ||
Line 44: | Line 41: | ||
| [[Stewards/PR|Public Relations]] | | [[Stewards/PR|Public Relations]] | ||
| Shannon Prior | | Shannon Prior | ||
− | |||
− | |||
− | |||
|- | |- | ||
| [[Stewards/Support|Support]] | | [[Stewards/Support|Support]] | ||
Line 53: | Line 47: | ||
| [[Stewards/IT|Systems Administration]] | | [[Stewards/IT|Systems Administration]] | ||
| Matthew Zeier and Corey Shields | | Matthew Zeier and Corey Shields | ||
+ | |- | ||
+ | | [[Stewards/Automation|Tools and Automation]] | ||
+ | | Clint Talbert and Lukas Blakk | ||
|- | |- | ||
| [[Stewards/QA|Quality Assurance]] | | [[Stewards/QA|Quality Assurance]] |
Revision as of 17:01, 27 September 2011
The Contributor Stewards program is a scalable way to bring in new people to all areas of the Mozilla community by having members of different teams be responsible for driving contributor growth for each project area. There are three parts to the program:
- Select someone on your team to be a steward responsible for helping contributors get involved in your activities.
- Add contributor growth and health targets to your quarterly goals.
- Make time for the steward to work with the Contributor Engagement team to improve the process for contributing to your project.
Teams that make this investment in contributor recruiting will become more effective at bringing people into their project and will be able to accomplish more as their team grows.
Anyone interested in community building would make a great Steward. We expect that Stewards will spend up to 5 hours a week on activities related to this role. This also doesn't need to be a long-term commitment and it is fine to have different people on a team rotate through this role.
See the Steward Program slides from the September 2011 All Hands for more details.
Contents
Areas
Functional Areas
Area | Steward |
---|---|
Coding | Dietrich Ayala, Kyle Huey, Brian Bondy and Josh Matthews |
Developer Documentation | Janet Swisher |
Labs | Desigan (Dees) Chinniah |
Localization | Zbigniew Braniecki (Gandalf) |
Mobile Development | Lucas Rocha |
Product Marketing | Gregory Jost |
Public Relations | Shannon Prior |
Support | Michelle Luna |
Systems Administration | Matthew Zeier and Corey Shields |
Tools and Automation | Clint Talbert and Lukas Blakk |
Quality Assurance | Anthony Hughes, Marcia Knous and Juan Becerra |
User Engagement | Chelsea Novak |
Web Development | Christie Koehler, Andy McKay, Rob Helmer, Dave Dash, Tim Watts and Les Orchard |
Geographic Areas
Area | Steward |
---|---|
Minneapolis/St. Paul | Scott Johnson |
Portland | Christie Koehler |
Toronto | Armen Zambrano Gasparnian |
Vancouver | Karen Esterly and Andy McKay |
San Francisco | Lukas Blakk |
Activities
Each team has unique needs that will require creating specific plans for improvement, but there are some general activities that apply to most project areas, such as:
- Assisting with the Contributor Life Cycle Audit
- Helping get contributors signed up to the phonebook
- Reviewing responses to inquiries from Get Involved page
- Writing up volunteer role descriptions (eg, Newsletter Coordinator)
- Working with Mozilla Representatives to promote your project
Resources
Contributor Channels
There are a number of channels you can use to get information out to existing and potential contributors about how to get involved in your project:
- Get Involved pages: over 300,000 visitors a month
- Want to help? form: over 2,000 inquiries a month
- about:mozilla newsletter: over 3,000 subscribers
- Mozillians YouTube channel: over 20 subscribers (just starting to grow this channel)
If you have any questions about any of these or would you to make use of them, let us know.
Peer Support
One of the best ways to learn more about Mozilla and get help is to talk with other people in the community. There are many ways to do this, but the following options are great forums for discussions about helping people get involved in the project.
- Contribute Group: a group that meets every other Thursday at 10 pacific to discuss issues related to helping people get involved in Mozilla.
- Community events: there are many Mozilla events run by volunteers all around the world and they can be very energizing experiences if you haven't been to one before. For example, read Matthew Zeier's post about an amazing experience he had attending community events in Argentina.
Skill Development
The following links have information that will help you improve your community building skills. Let us know what else we could add that would be helpful.
- Documentation
- Training
- TBD
- Sessions
- TBD
Special Interest Groups
The Mozilla Reps (ReMo) program aims to empower and support volunteer Mozillians who want to become official representatives of Mozilla. Tapping into this group of people can be a great way to spread the word about contribution opportunities for your project and to get more people involved.
Local Groups
There may be groups near you that aren't necessarily related to Mozilla, but can be good places to go to meet others interested in community building or who have an interest in Mozilla's mission. If you know of one of these groups, add it to this list.
Tools
Community building online would not be possible without tools to help with the process. The community is full of a number of tools, but there has been a lack of some key pieces of volunteer management infrastructure that the Contributor Engagement team is now putting in place. Learn more about what's coming:
Communication
- mozillians or remo channels for now?
To Do
- Add link to phonebook profiles for each Steward when phonebook goes live.
- Add advice/best-practices in reaching out to local communities and events like this VanCX.