Changes

Jump to: navigation, search

EngineeringProductivity

2,215 bytes added, 21:30, 3 August 2015
no edit summary
See our [[Auto-tools/The_Ateam|Team Roster]] for a list of people on the team; find us on IRC on #ateam; e-mail us at auto-tools__at__mozilla_dot_com (internal list) or mozilla-tools__at__lists_dot_mozilla.org (external mailing list).
 
Many of us blog about the things we work on; you can check [http://planet.mozilla.org/ateam/ our team planet] for a feed of these.
== What We Work On ==
We generally don't write functional tests which are run in the harnesses we own, although we may help out here from time to time, particularly when this is done in conjunction with developing a new harness. Our interests here are empowering developers to write their own tests, but we sometimes contribute tests here as part of the bootstrapping process. Ultimately, as with unit tests, developers are best-suited to writing functional tests and understanding overall test coverage and design.
 
== Meetings ==
 
Everyone loves meetings, right? We have a [[Auto-tools/Meetings|fortnightly meeting]], every other Monday at 10am US Pacific Time. We typically discuss status, new projects, have demonstrations of new tools and features, and sometimes even bikeshed. All are welcome, please join us!
 
== Goals and Projects ==
 
We set and deliver [[/Goals|quarterly goals]], which is usually a good place to see what we're up to. If you have some work you'd like to see us incorporate into our goals, fill out our [https://bugzilla.mozilla.org/form.automative project request form].
 
For a list of projects that we own, see [[Auto-tools/Projects|Project Central]].
 
Periodic team updates are posted to the [https://groups.google.com/forum/#!forum/mozilla.tools mozilla.tools] mailing list.
 
== Getting Involved ==
 
We love contributors! We see community members as one of the keys to our success, and actively encourage and mentor their contributions. Working on the testing, build, and automation systems at Mozilla is a fantastic introduction to Mozilla development. There are two great ways to help - either by joining an existing project, or taking on one of our "starter" projects to help you learn your way around.
* [http://ateam-bootcamp.rtfd.org A-team bootcamp] - This covers the basics of getting started as an A-Team contributor.
* [[auto-tools/Projects|Existing Project]] -- Look over our [[auto-tools/Projects|projects]] list and see if there is anything that you'd like to help with.
* Good First Bugs -- Just want a bug to try out? Find a few [http://www.joshmatthews.net/bugsahoy/?automation=1 here] and we can help you get started
* [[auto-tools/New_Contributor|New Contributor?]] -- Check out [[auto-tools/New_Contributor|this page]] for an overview of tools and resources to help you out with that first project.
* Check out the [[Auto-tools/New_Contributor/Skills_and_Areas|skills and areas]] of the team to see how you can fit in and help out.
If you have questions, or if you want to sign up, please come find us on [http://irc.mozilla.org IRC] in #ateam.
Confirm
1,905
edits

Navigation menu