Confirmed users, Bureaucrats and Sysops emeriti
421
edits
(nits) |
|||
Line 44: | Line 44: | ||
= Diamond Bugs = | = Diamond Bugs = | ||
Marked as [diamond] on the whiteboard, this label doesn't speak to a bug's difficulty, but certainly speaks to its importance. Diamond bugs are bugs that have been brought up as candidate bugs for | Marked as [diamond] on the whiteboard, this label doesn't speak to a bug's difficulty, but certainly speaks to its importance. Diamond bugs are bugs that have been brought up as candidate bugs in engineering's priority-triage processes - for example, front-end engineering's Firefox Priority Backlog meetings - but aren't assigned to an engineer by the end of the triage process. | ||
A diamond bug should always have a mentor associated with it. These bugs are an organizational priority, and their successful completion is important; contributors taking on diamond bugs should do their best to communicate their progress frequently in the bug, and anyone mentoring a diamond bug should do their best to turn around a contributor's questions or feedback promptly. | A diamond bug should always have a mentor associated with it. These bugs are an organizational priority, and their successful completion is important; contributors taking on diamond bugs should do their best to communicate their progress frequently in the bug, and anyone mentoring a diamond bug should do their best to turn around a contributor's questions or feedback promptly. |