Webtools/Audit2012: Difference between revisions
(Created page with "In Q1 2012, we will undertake an audit of the toolchain of web apps on the critical path to ship Firefox. For each webapp: * Bug audit and triage * Safety check: monitoring, re...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= Webtools audit = | |||
* Project owner: Laura Thomson laura@mozilla.com | |||
= Overview = | |||
In Q1 2012, we will undertake an audit of the toolchain of web apps on the critical path to ship Firefox. | In Q1 2012, we will undertake an audit of the toolchain of web apps on the critical path to ship Firefox. | ||
For each | This project came about because the more tools our team works on, the more problems we discover. There are apps that would block ship if they were broken or exploited that don't have owners, run on unmonitored VMs, have no backups, run painfully slowly, etc. | ||
The goal is to map out the webapps that are in the product-shipping workflow, understand the importance of each, and make sure each one has an appropriate level of support, documentation, and performance. | |||
Examples of these apps include ones we already work on or have contributed to: | |||
* Socorro | |||
* graphs.mozilla.org | |||
* Elmo | |||
* tbpl | |||
* Verbatim | |||
* AUS | |||
and ones we don't or don't yet: | |||
* mxr | |||
* dxr | |||
* Pontoon | |||
* Bouncer | |||
* <your app here> | |||
For each of these webapps: | |||
* Find or assign owner | |||
If unowned or neglected: | |||
* Bug audit and triage | * Bug audit and triage | ||
* Safety check: monitoring, redundancy, backups, etc | * Safety check: monitoring, redundancy, backups, etc | ||
* Documentation check | * Documentation check | ||
* Future plan, depending on the above | |||
* Future plan, depending on the above | |||
This project will require input from Platform, RelEng, IT, and potentially InfraSec. | |||
Latest revision as of 18:30, 29 December 2011
Webtools audit
- Project owner: Laura Thomson laura@mozilla.com
Overview
In Q1 2012, we will undertake an audit of the toolchain of web apps on the critical path to ship Firefox.
This project came about because the more tools our team works on, the more problems we discover. There are apps that would block ship if they were broken or exploited that don't have owners, run on unmonitored VMs, have no backups, run painfully slowly, etc.
The goal is to map out the webapps that are in the product-shipping workflow, understand the importance of each, and make sure each one has an appropriate level of support, documentation, and performance.
Examples of these apps include ones we already work on or have contributed to:
- Socorro
- graphs.mozilla.org
- Elmo
- tbpl
- Verbatim
- AUS
and ones we don't or don't yet:
- mxr
- dxr
- Pontoon
- Bouncer
- <your app here>
For each of these webapps:
- Find or assign owner
If unowned or neglected:
- Bug audit and triage
- Safety check: monitoring, redundancy, backups, etc
- Documentation check
- Future plan, depending on the above
This project will require input from Platform, RelEng, IT, and potentially InfraSec.