Contribute/IT: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
What are the steps someone can take to get involved in your project and learn enough to be able to start scratching their own itch? | What are the steps someone can take to get involved in your project and learn enough to be able to start scratching their own itch? | ||
1. | 1. Join the public #it channel and say hi. | ||
2. | 2. | ||
Revision as of 16:13, 27 September 2011
Steward
Matthew Zeier and Corey Shields
Contribution Paths
What are the steps someone can take to get involved in your project and learn enough to be able to start scratching their own itch?
1. Join the public #it channel and say hi.
2.
3.
4. Scratch your own itch
Brainstorming for entry points
Challenge: There are sysadmin tasks for contributors to do but it requires establishing a certain level of trust first. What useful activities are there for new people that will help build up that trust?
- Subscribe to a mailing list or IRC channel and say hi
- Set up a mirror -- may only apply to institutions that have spare servers and bandwidth
- If setting up mirrors isn't a great fit for individuals is there a need for providing support to institutions that act as mirrors or testing the mirror network?
- Desktop support for Mozilla Spaces (maybe also at college computer labs, libraries, etc?)
- Combine entry points with Release Engineering if there's reasonable overlap?
- Help with Air Mozilla
- Look at what other open source projects are doing, eg Apache's Infrastructure team
Goals
What goals does your team have for bringing in new contributors to your project area?
Metrics
What data is available to measure if we're meeting your goals?
- Number of mirrors?
- Patches to Air Mozilla?