Purpose of Meeting

Recurring triage sessions to accomplish these community goals:

Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions.
Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.
Experiments: Discuss and provide feedback for WebExtensions Experiments.

Next Meeting

TBD

When scheduled, meetings are on Tuesdays at 10:30am Pacific (17:30 UTC)
Need help converting to your local time? Click here.
Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU
IRC: irc.mozilla.org, #Addons channel
To join from a telephone, dial one of the following numbers depending on your nearest location:
- US Toll Free +1 800 707 2533, pin 2000, conf 8960
- US/CA/Mountain View +1 650 903 0800, extension 2000, 8960
- US/CA/San Francisco: +1 415 762 5700, extension 2000, 8960
- US/OR/Portland: +1 971 544 8000, extension 2000, 8960
- CA/BC/Vancouver: +1 778 785 1540, extension 2000, 8960
- CA/ON/Toronto: +1 416 848 3114, extension 2000, 8960
- UK/London: +44 (0)207 855 3000, extension 2000, 8960
- FR/Paris: +33 (0) 184 883 737, Press 1 for English or 2 for French, extension 2000, 8960
- DE/Berlin: +49 30 983 333 000, extension 2000, 8960
- NZ/Auckland: +64 9 555 1100, extension 2000, 8960

We normally spend 5 minutes per bug
The more information in the bug, the better
The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details
If you're interested in submitting a proposal for a new API, please read the WebExtensions Vision.

Bugs marked "design-decision-needed" should be:

Bugs marked "design-decision-approved" should have:

These are determined from the Monday WebExtensions triage. They are APIs we need more discussion on.

These are APIs we would like to have. They should meet the triage criteria listed above.

Submit your WebExtensions Experiment by opening an issue on the web-ext-experiments github repo.
Be sure to include the following in your issue:
- Link to where your experiment is located
- A quick overview of what it does
- Any Bugzilla bugs that it might address
- If you’d like to move your repository over to this organisation and we can create a repository for you
A comment will be added to the issue when your WebExtensions Experiment has been added to a meeting agenda.