WebExtensions/AdvisoryGroup: Difference between revisions
Jump to navigation
Jump to search
(→Flow) |
(→Flow) |
||
| Line 4: | Line 4: | ||
=Flow= | =Flow= | ||
* 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. | |||
Bugs marked with these [design-decision...] are 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] | ||
Revision as of 19:27, 23 November 2016
WebExtensions Advisory Group is a cross-disciplinary body responsible for guiding the development of WebExtensions as it branches out into new APIs beyond the basic level of Chrome parity.
Bugs should be labelled with "[design-decision-needed]" can be found .
Flow
- 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.
Bugs marked with these [design-decision...] are talked about in the bi-weekly community meeting:
- Mark a bug as [design-decision-needed], existing bugs
- If it sounds good it will get marked as [design-decision-approved], existing bugs
- Start sending in some patches for [design-decision-approved] bugs :)
Responsibilities
- Steering WebExtension API development
- Recommendations of new APIs.
- Guidance on API requests, if an API should be implemented.
- Feedback to people requesting APIs and alternatives.
- Evaluating experimental APIs and see if they should be included.
Members
- Kev Needham: Product
- Daniel Veditz: Security
- Adam Roach: Engineering
- Gijs Kruitbosch: Firefox front end
- Michael Kaply: Enterprise
- Dan Callahan: Developer relations
... and most of the normal WebExtension development team.
Meeting Notes
Next meeting: TBD
Running document: https://docs.google.com/document/d/1qCIUX0LavYixkzwan8IcSYeut4zQiCkJbrMVpSEm5Lk/edit#