49
edits
Add-ons: Difference between revisions
Updated list of peoples, removed reference to defunct phonebook and mozillians site, remove some obsolete sections, update some links
Caitmuenster (talk | contribs) (→Who: removed cgrebs :( and Shell) |
(Updated list of peoples, removed reference to defunct phonebook and mozillians site, remove some obsolete sections, update some links) |
||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 18: | Line 18: | ||
Engineering Manager: | Engineering Manager: | ||
* | * Shane Caraveo (:mixedpuppy) | ||
Engineering Leads: | Engineering Leads: | ||
* | * William Durand (:willdurand) | ||
* Mathieu Pillard | * Mathieu Pillard | ||
Engineers: | Engineers: | ||
* Luca Greco (:rpl) | |||
* Luca Greco ( | * Tomislav Jovanovic (:zombie) | ||
* Tomislav Jovanovic ( | * Andrew Williamson | ||
* Rob Wu (:robwu) | |||
* Andrew Williamson | |||
* Rob Wu ( | |||
Looking for the [ | Looking for the [https://mozilla.github.io/addons/server/push-duty.html push duty roster] maybe? | ||
=== | === Product Management and [[Add-ons/ACE|Community Experience]] === | ||
* | * Scott DeVaney, Sr. Editorial Manager | ||
* Andreas Wagner, Product Operations Manager | |||
* Abhishek Nagekar, Add-ons Security Engineer | |||
=Get in touch= | |||
=== | ==Reporting problems== | ||
=== | ===Security Vulnerabilities=== | ||
If you discover an add-on security vulnerability, even if the add-on is not hosted on a Mozilla site, please notify us. We will work with the developer to correct the issue. Please report security vulnerabilities [https://www.mozilla.org/about/governance/policies/security-group/bugs/ confidentially] in [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org&component=Add-on%20Security&maketemplate=Add-on%20Security%20Bug&bit-23=1&rep_platform=All&op_sys=All Bugzilla]. | |||
= | ===Bugs on addons.mozilla.org=== | ||
If you find a problem with the site, we'd love to fix it. Please [https://github.com/mozilla/addons/issues/new file a bug report] and include as much detail as possible. | |||
==Contact us== | |||
* [[Matrix]]: | * [[Matrix]]: | ||
** Add-ons: support for extensions, themes, and API development | ** Add-ons: support for extensions, themes, and API development | ||
** Add-on Reviewers: add-on reviews and policy | ** Add-on Reviewers: add-on reviews and policy | ||
** AMO: addons.mozilla.org bugs and development | ** AMO: addons.mozilla.org bugs and development | ||
* Community Forum: https://discourse.mozilla.org/c/add-ons/ | |||
* | * Blog: https://blog.mozilla.org/addons/ | ||
== Meetings == | == Meetings == | ||
From 2025 until 2018, the add-ons team held regular public meetings, with meeting notes archived at [[Add-ons/Contribute/Triage]]. | |||
From 2021, members of the add-ons team participate in biweekly WebExtensions Community Group (WECG) meetings, with meeting notes published at [https://github.com/w3c/webextensions/tree/main/_minutes#readme https://github.com/w3c/webextensions/tree/main/_minutes]. | |||
===Contribute to Add-ons=== | ===Contribute to Add-ons=== | ||
| Line 104: | Line 84: | ||
Everything else is tracked on Github. The main repositories are: | Everything else is tracked on Github. The main repositories are: | ||
* [ | * [https://github.com/mozilla/addons-server addons server] | ||
* [ | * [https://github.com/mozilla/addons-frontend addons frontend] | ||
* [ | * [https://github.com/mozilla/addons-linter addons linter] | ||
* [https://github.com/mozilla/web-ext web-ext tool] | |||
* [https:// | |||
== Multi-process Firefox == | == Multi-process Firefox == | ||
For information on the roll out of multi-process Firefox and add-ons, please see [https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule the schedule] | For historical information on the roll out of multi-process Firefox and add-ons leading up to the Firefox 57 release, please see [https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule the schedule] | ||
===Communications Calendar=== | ===Communications Calendar=== | ||
Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing. | Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing. | ||
{{#widget:Widget:Google Calendar | {{#widget:Widget:Google Calendar | ||
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ | |id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ | ||
| Line 129: | Line 104: | ||
* Simplify continual planning, so the plan matches reality. | * Simplify continual planning, so the plan matches reality. | ||
* Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs) | * Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs) | ||
==Triage Guidelines== | ==Triage Guidelines== | ||
===Bugzilla=== | ===Bugzilla=== | ||
* '''Priorities''' follow this Standard: | * '''Priorities''' follow this Standard: | ||
** Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release. | ** Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release. | ||
| Line 150: | Line 122: | ||
===Github=== | ===Github=== | ||
*Added labels to [https://mozilla.github.io/addons/repositories.html add-ons repositories] for: | |||
*Added labels to [ | |||
**'''P1''' - either bug we would block next targeted featured for or a time-critical major bug | **'''P1''' - either bug we would block next targeted featured for or a time-critical major bug | ||
**'''P2''' - either feature we'd really like, but wouldn't delay releasing the P1's for (good to look at after passing milestone). or Major impact bug, considering severity × probability. Not a blocker for shipping. | **'''P2''' - either feature we'd really like, but wouldn't delay releasing the P1's for (good to look at after passing milestone). or Major impact bug, considering severity × probability. Not a blocker for shipping. | ||
| Line 168: | Line 139: | ||
* If the developer is unsure, then just leave it alone or mark in the whiteboard with "[needs-more-triage]", this indicates they've looked at it, but aren't sure. | * If the developer is unsure, then just leave it alone or mark in the whiteboard with "[needs-more-triage]", this indicates they've looked at it, but aren't sure. | ||
* We'll have a regular weekly meeting to catch all the untriaged bugs and decide what to do with them. | * We'll have a regular weekly meeting to catch all the untriaged bugs and decide what to do with them. | ||
* [https://addons-pm.herokuapp.com/dashboards/webext/ WebExtensions dashboard for triage] | |||
The goal of this is to allow the developers to triage the bugs and spot major regressions, but when we get to a triage meeting it shouldn't be the first time people have looked at the bug and so can have a good conversation about the bug. | The goal of this is to allow the developers to triage the bugs and spot major regressions, but when we get to a triage meeting it shouldn't be the first time people have looked at the bug and so can have a good conversation about the bug. | ||
| Line 173: | Line 145: | ||
===AMO=== | ===AMO=== | ||
*Experimenting with [https://wiki.mozilla.org/Add-ons#Github new triage process], will change as needed | *Experimenting with [https://wiki.mozilla.org/Add-ons#Github new triage process], will change as needed | ||
===Add-ons Manager=== | ===Add-ons Manager=== | ||