Engagement/MDN Durable Team/Processes: Difference between revisions

Engagement/MDN Durable Team/Processes (view source)

Revision as of 23:27, 15 June 2018

340 bytes added , 15 June 2018

→‎Triaging Requests

Jswisher

canmove, Confirmed users

1,953

edits

@@ Line 39: / Line 39: @@
 * P1: Will be done by staff during the current quarter
 * P2: Will be done by staff during the next quarter
-* P3: Will be done by staff eventually
+* P3: Will be done by staff "eventually"
 * P4: Not used
 * P5: Valid issue that will not be done by staff; patches are welcome from volunteer contributors.
-Emergency work may be started immediately, and tracked as "other" tasks not contributing to a user story. Bugs in current work may be added as new tasks to existing user stories. Other work will be deferred, either as user stories in future sprints or deferred indefinitely. Leaving a bug open is rarely a commitment to fix the bug. P1 and P2 bugs are reviewed at the end/beginning of each quarter to determine if their priority is still valid.
+Leaving a bug open is rarely a commitment to fix the bug. P1 and P2 bugs are reviewed at the end/beginning of each quarter to determine if their priority is still valid.
+It's a bit awkward to have some types of work represented as Bugzilla bugs, while the majority of MDN work is represented as GitHub issues. When a Bugzilla issue is planned to be worked on during a sprint, a GitHub issue should be created for it, containing a link to the Bugzilla issue. Use GitHub (and ZenHub) for estimation and status-tracking; use Bugzilla for discussion.
+Emergency work can be started immediately and may pre-empt work that was previously planned for the sprint; in such a case, affected team members should confer with the product owner to decide what to do with other affected work.
 '''Tools'''