We could do better at the "typo test"
Bug #1078393 reported by
Evan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Errors |
Confirmed
|
High
|
Unassigned | ||
Bug Description
Sit a programmer down and ask them to fix a typo somewhere within the Ubuntu Error Tracker infrastructure. Measure the time it takes for them to learn the codebase, make the change, propose it, and get it accepted then deployed to production.
I fear this number is quite high. There's a lot more we could do to lower this number. This bug tracks our efforts.
http://
http://
Revision history for this message
| Matthew Paul Thomas (mpt) wrote | #1 |
| Changed in errors: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| description: | updated |
| description: | updated |
To post a comment you must log in.
To know whether this bug is fixed, it will need a measurement. E.g. "this bug will be fixed when the last two new contributors we watched could both make a trivial fix within 30 minutes".