Confirmed users
3,376
edits
(ateam handbook) |
(added guidelines section) |
||
| Line 52: | Line 52: | ||
=== Overview === | === Overview === | ||
Work in progress effort to create an index for all existing/WIP automation tools - [[Auto-tools/Projects/Everything|Here]]. | Work in progress effort to create an index for all existing/WIP automation tools - [[Auto-tools/Projects/Everything|Here]]. | ||
=== Guidelines === | |||
Guidelines for what to include in project documentation: | |||
* The goals of the project | |||
* Why the project is important to Mozilla | |||
* List out who to contact, mentors, active developers | |||
* Dependencies on other projects/teams and priority of the project within the ateam | |||
* Documentation for how to use the project (or how it will be used) | |||
* How to setup / develop / test the project | |||
* Milestones and features to be developed (bugzilla table) | |||
* Good first bugs and how to get started (bugzilla table) | |||
* How to submit a patch | |||
* Coding style guidelines and expectations | |||
When setting the priority of a project, consider this scale as a starting point: | |||
* 1 - This is a stated goal for the current quarter | There are active people working on this | Other projects/teams depend on this completing | |||
* 2 - There are active people working on this | We are committed to delivering at least one milestone in the current quarter | |||
* 3 - This is an project that we and others believe would be beneficial to Mozilla, but we haven't promised to deliver it on a specific timeline. There are clear plans and maybe a prototype of one or more milestones to start with | |||
* 4 - This is a good idea or a project that we worked on in the past which could use maintenance. We don't have resources for this now, but still feel it is a valuable project! | |||
=== Firefox OS === | === Firefox OS === | ||