Confirmed users
4,467
edits
Contribute/Automation: Difference between revisions
→Define Contribution Opportunities
| Line 20: | Line 20: | ||
A: The A-Team needs people that work on javascript, python, and web design to help out with a bunch of projects. You can see [https://wiki.mozilla.org/Auto-tools/New_Contributor/Skills_and_Areas our areas where we could use help] and [https://wiki.mozilla.org/Auto-tools/Projects our current and past projects] to see what types of things we do. | A: The A-Team needs people that work on javascript, python, and web design to help out with a bunch of projects. You can see [https://wiki.mozilla.org/Auto-tools/New_Contributor/Skills_and_Areas our areas where we could use help] and [https://wiki.mozilla.org/Auto-tools/Projects our current and past projects] to see what types of things we do. | ||
Release Engineering needs people to help with simple bugs that don't require account permissions. The Try Server/Trychooser is a great place to start, so is Autoland. The details are outlined in [https://wiki.mozilla.org/ReleaseEngineering:Contribute https://wiki.mozilla.org/ReleaseEngineering:Contribute]. A beginner in Python could learn a lot working on some of our automation scripts and digging into buildbot code. We have instructions to help contributors set up local staging environments to be able to run the build & release automation to test their contributions. | |||
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. | 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. | ||