Confirmed users
1,158
edits
WebExtensions/AdvisoryGroup: Difference between revisions
Jump to navigation
Jump to search
→Flow
(→Flow) |
(→Flow) |
||
| Line 4: | Line 4: | ||
=Flow= | =Flow= | ||
When a bug comes into WebExtensions, there is a multiple triage process. Advisory group is the location of last resort for when we need help. Before hand we would expect at least a bug to: | |||
Be marked with [design-decision-need] and talked about in the bi-weekly community meeting: | |||
* Mark a bug as [design-decision-needed], [https://mzl.la/2d73PBq existing bugs] | * Mark a bug as [design-decision-needed], [https://mzl.la/2d73PBq existing bugs] | ||
* If it sounds good it will get marked as [design-decision-approved], [https://mzl.la/2cXI6IH existing bugs] | * If it sounds good it will get marked as [design-decision-approved], [https://mzl.la/2cXI6IH existing bugs] | ||
* Start sending in some patches for [design-decision-approved] bugs :) | * Start sending in some patches for [design-decision-approved] bugs :) | ||
* If we still struggle with the bug, we'll mark it with [advisory-group] | |||
Bugs marked with [advisory-group] will be handled in the regular advisory group meeting: | |||
* Mark a bug as [advisory-group], this should be reserved for bugs that can't be resolved by the community. For example, sometimes security questions need more input. [https://mzl.la/2gfpi9s Existing bugs] | |||
=Responsibilities= | =Responsibilities= | ||