EngineeringProductivity/Projects

From MozillaWiki
Jump to: navigation, search

Project Table

We have many projects in different states. This table below should highlight what is being done and upcoming work in the future. If you want to get involved, look for a higher [Friendly] score!

  • Priority score of 1 is the highest, 3 is the lowest
  • Friendly score of 10 is the highest, 1 is the lowest

Click here to learn more about the guidelines and priority.

Project Name Link to Details/Docs Contact Info Friendly (1-10) Priority (1-3)
ActiveData [wiki] ekyle 7 1
Autophone [AutoPhone Wiki] bc 6 2
Bugzilla [BMO Wiki] dkl,dylan,glob,mcote 9 2
Development Metrics [Wiki] ekyle 2 2
Marionette [Marionette Wiki] ato,AutomatedTester,maja_zf,jgriffin 7 1
Firefox UI Tests [Firefox UI Tests Wiki] whimboo,maja_zf 8 1
MozReview [MozReview Wiki] mcote 6 1
MozRegression [Mozregression Wiki] wlach 6 3
Other Tools [Other Wiki] jgriffin 6 2
Stockwell [Stockwell Wiki (intermittent oranges)] jmaher 6 1
Talos [Talos Wiki] jmaher 10 3
Test Harnesses [Wiki] ahal,jgriffin,jmaher,ted 9 2
Test Informant [Test Informant Wiki] ahal 6 3
Treeherder [Treeherder Wiki] camd,emorley,jgraham,wlach 7 1
Perfherder [Perfherder Wiki] wlach 7 1
Web-Platform-Tests [web-platform-tests Wiki] jgraham 8 3

Maintenance Project Table

We have many projects in different states. This table below lists the projects we have done and left off in some state. Most of these are still running and we are responsible for maintenance as it is needed. There is no specific goal, deliverable, roadmap, milestones planned for these projects.

  • Priority score of 1 is the highest, 3 is the lowest
  • Friendly score of 10 is the highest, 1 is the lowest

Click here to learn more about the guidelines and priority.

Project Name Link to Details/Docs Contact Info Friendly (1-10) Priority (1-3)
BugzFeed [BMO Change Notification] mcote 4 3
BMO/ES [BMO Elasticsearch] ekyle 6 3
Charts [Charts Wiki] ekyle 7 2
DevTools Harness [Wiki] ted 6 3
OrangeFactor [OrangeFactor Wiki] jgriffin,mcote 3 3
Ouija [Ouija Wiki] dminor,jmaher 4 3
Pulse [Pulse Wiki] mcote 5 3
Structured Logging [Structured Logging Wiki] ahal,chmanchester,jgraham 8 3

Retired and Deprecated Project Table

These projects have either been retired completely, or further work on them has been deprecated in favor of newer alternatives.

Project Name Link to Details/Docs Contact Info Post-mortem
Alert Manager [AlertManager Wiki] dminor,jmaher
Datazilla [Datazilla ReadTheDocs] camd,mdoglio,wlach [post-mortem]
dzAlerts [Alerts Wiki] ekyle
Eideticker [Eideticker Wiki] davehunt,wlach [post-mortem]

Other Projects

More (mostly maintenance and inactive) projects are listed at https://wiki.mozilla.org/Auto-tools/Projects/Everything

Guidelines

The guidelines are evaluated based on the link we have to documentation (wiki, readme.md, readthedocs, etc.) This link should contain the information or in the first page of text have a link to additional information so that we can easily learn about the project.

Guidelines for what to include in project documentation:

  • The goals of the project
  • Why the project is important to Mozilla and/or the A-Team
  • Dependencies on other projects/teams, and its place in the greater ecosystem
  • List out who to contact, mentors, active developers
  • 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, link to well annotated github issues, etc.)
  • Good first bugs and how to get started (bugzilla table, link to well annotated github issues, etc.)
  • 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!