Add-ons: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Get in touch: updated "get in touch" section)
(Updated list of peoples, removed reference to defunct phonebook and mozillians site, remove some obsolete sections, update some links)
 
(6 intermediate revisions by 4 users not shown)
Line 18: Line 18:


Engineering Manager:
Engineering Manager:
* Stuart Colville ([https://phonebook.mozilla.org/#search/Stuart%20Colville internal], [https://muffinresearch.co.uk/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])
* Shane Caraveo (:mixedpuppy)


Engineering Leads:  
Engineering Leads:
* Shane Caraveo ([https://phonebook.mozilla.org/#search/Shane%20Caraveo internal], [https://mozillians.org/en-US/u/scaraveo/ Mozillian Profile])
* William Durand (:willdurand)
* Mathieu Pillard ([https://phonebook.mozilla.org/#search/Mathieu%20Pillard internal]])
* Mathieu Pillard


Engineers:
Engineers:
* William Durand ([https://phonebook.mozilla.org/?search/William%20Durand internal]), [https://mozillians.org/en-US/u/willdurand/ Mozillian Profile]
* Luca Greco (:rpl)
* Luca Greco ([https://mozillians.org/en-US/u/luca/ Mozillian Profile])
* Tomislav Jovanovic (:zombie)
* Tomislav Jovanovic ([https://mozillians.org/en-US/u/zombie/ Mozillian profile])
* Andrew Williamson
* Bob Silverberg ([https://phonebook.mozilla.org/#search/Bob%20Silverberg internal])
* Rob Wu (:robwu)
* Andrew Williamson ([https://phonebook.mozilla.org/?search/eviljeff internal], [https://mozillians.org/en-US/u/eviljeff/ Mozillian Profile])
* Rob Wu ([https://phonebook.mozilla.org/?search/Rob%20Wu internal], [https://mozillians.org/en-US/u/robwu/ Mozillian Profile])


Looking for the [http://addons.readthedocs.org/en/latest/server/push-duty.html push duty roster] maybe?
Looking for the [https://mozilla.github.io/addons/server/push-duty.html push duty roster] maybe?
 
=== User Experience ===
* Aaron Benson, UX Designer ([https://people.mozilla.org/p/r--M7dY4lqwUiuGc4Hnliswdg== internal])
 
Partial support:
* Emanuela Damiani, UX Designer ([https://phonebook.mozilla.org/?search/emanuela internal])


=== Product Management and [[Add-ons/ACE|Community Experience]] ===
=== Product Management and [[Add-ons/ACE|Community Experience]] ===
* Amy Tsay, Add-ons Lead ([https://phonebook.mozilla.org/#search/tsay internal], [https://mozillians.org/en-US/u/amyt/ mozillians profile])
* Scott DeVaney, Sr. Editorial Manager
* Jorge Villalobos, Product Manager ([https://phonebook.mozilla.org/#search/jorge internal], [https://mozillians.org/en-US/u/jorgev/ mozillians profile])
* Andreas Wagner, Product Operations Manager
* Scott DeVaney, Sr. Editorial Manager ([https://phonebook.mozilla.org/#search/devaney internal], [https://mozillians.org/en-US/u/sdevaney/ mozillians profile])
* Abhishek Nagekar, Add-ons Security Engineer
* Caitlin Neiman, Community Manager ([https://phonebook.mozilla.org/#search/neiman internal], [https://mozillians.org/en-US/u/cneiman/ mozillians profile])
* Andreas Wagner, Reviewer ([https://phonebook.mozilla.org/#search/andreas%20wagner internal], [https://mozillians.org/en-US/u/TheOne/ mozillians profile])
* Philipp Kewisch, WebExtensions API Product Manager & Reviewer ([https://phonebook.mozilla.org/#search/kewisch internal], [https://mozillians.org/en-US/u/kewisch/ mozillians profile])
 
=== QA ===
* Krupa Raj ([https://phonebook.mozilla.org/#search/krupa internal], [https://mozillians.org/en-US/u/kruparaj/ mozillians profile])
* Victor Carciu
* Madalin Cotetiu
* Valentina Peleskei
* Cosmin Badescu
* Rares Macarie


=Get in touch=
=Get in touch=
Line 61: Line 42:


===Security Vulnerabilities===
===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] or by emailing amo-admins@mozilla.com.
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===
===Bugs on addons.mozilla.org===
Line 76: Line 57:
== Meetings ==
== Meetings ==


Please see the add-ons calendar:
From 2025 until 2018, the add-ons team held regular public meetings, with meeting notes archived at [[Add-ons/Contribute/Triage]].
* Calendar: [https://www.google.com/calendar/embed?src=mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com  Preview], [https://www.google.com/calendar/ical/mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com/public/basic.ics iCal import]
 
Minutes:


Click into the calendar event to find links to publicly available meeting minutes.  
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 106: Line 84:
Everything else is tracked on Github. The main repositories are:
Everything else is tracked on Github. The main repositories are:


* [http://github.com/mozilla/addons-server addons server]
* [https://github.com/mozilla/addons-server addons server]
* [http://github.com/mozilla/addons-frontend addons frontend]
* [https://github.com/mozilla/addons-frontend addons frontend]
* [http://github.com/mozilla/addons-linter addons linter]
* [https://github.com/mozilla/addons-linter addons linter]
 
* [https://github.com/mozilla/web-ext web-ext tool]
== Trello ==
 
We use Trello for planning out roadmaps. A Trello card normally relates to multiple bugs, or a larger feature.
 
* [https://trello.com/b/PC9kB14s/add-ons-engineering-pipeline Engineering Pipeline]


== 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.
<p></p>
 
{{#widget:Widget:Google Calendar
{{#widget:Widget:Google Calendar
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
Line 131: 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)
<p> </p>
<p> </p>


==Triage Guidelines==
==Triage Guidelines==
===Bugzilla===
===Bugzilla===
<p> </p>
* '''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 152: Line 122:


===Github===
===Github===
<p> </p>
*Added labels to [https://mozilla.github.io/addons/repositories.html add-ons repositories] for:
*Added labels to [http://addons.readthedocs.org/en/latest/repositories.html add-ons repositories] for:
**'''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 170: 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 175: 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  
*[https://waffle.io/mozilla/addons?source=mozilla%2Faddons-server,mozilla%2Faddons.mozilla.org-mod,mozilla%2Famo-validator,mozilla%2Faddons-frontend,mozilla%2Faddons-linter,mozilla%2Faddons,mozilla%2Fdispensary Triage Query]


===Add-ons Manager===
===Add-ons Manager===

Latest revision as of 14:05, 22 January 2026

What

Mission: Add-ons enable Firefox users to personalize their web experience.

This is the home page for Add-ons at Mozilla.

Including but not limited to:

Who

Note: This is a list of people employed by Mozilla. But we are way more than that, please add yourselves in if you want.

Engineering

Engineering Manager:

  • Shane Caraveo (:mixedpuppy)

Engineering Leads:

  • William Durand (:willdurand)
  • Mathieu Pillard

Engineers:

  • Luca Greco (:rpl)
  • Tomislav Jovanovic (:zombie)
  • Andrew Williamson
  • Rob Wu (:robwu)

Looking for the push duty roster maybe?

Product Management and 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 confidentially in Bugzilla.

Bugs on addons.mozilla.org

If you find a problem with the site, we'd love to fix it. Please file a bug report and include as much detail as possible.

Contact us

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.

Contribute to Add-ons

Support user freedom by helping to keep Firefox the most customizable browser available.

Status & Roadmap

Bugs are stored in one of two places depending upon the project. Roadmaps are all stored in Trello.

Bugzilla

Anything that has to land in Firefox or Firefox for Android must have a Bugzilla bug. So most of the bugs are tracked in there.

Bugs:

Github

Everything else is tracked on Github. The main repositories are:

Multi-process Firefox

For historical information on the roll out of multi-process Firefox and add-ons leading up to the Firefox 57 release, please see the schedule

Communications Calendar

Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing.

Error in widget Widget:Google Calendar: Unable to load template 'wiki:Widget:Google Calendar'

Product Backlog

  • Improve work prioritization, so the team is always working on the most important features.
  • 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)

Triage Guidelines

Bugzilla

  • Priorities follow this Standard:
    • Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release.
    • Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping. For Features we'd really like it, but wouldn't hold shipping for it.
    • Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product.
    • Priority 4 - Not used.
    • Priority 5 - Low-impact. Something we won't fix, but would accept patches for.

  • Importance will be left at "normal" unless a bug is on the line of being one Priority higher and lower - and then will be marked "Major" or "Minor" accordingly. If a bug has been marked "critical" or "blocker," that bug should be made a P1.

  • Optional Whiteboard tag
    • Adding a short descriptive area tag in the whiteboard when possible, to visually group bugs quickly in a list. ex: "[tabs] triaged"
  • Triaged bug mark-up
    • Adding triaged tag to the end of the Whiteboard for bugs that have been assigned a priority, so we know what has been triaged. No [] needed

Github

  • Added labels to add-ons repositories for:
    • 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.
    • backlog - We know it's not in our immediate plans or roadmaps - but it's been noted
  • Added column to waffle boards for "triaged"
    • Move bugs from untriaged to triaged column after they've been looked at and Prioritized.

Common Bug Queries

Webextensions

WebExtensions Triage process

  • Bugs are triaged by developers as they come in and developers have chance to look at them.
  • Developers will give the bug a priority (P1,2,3 or 5) and move to the appropriate component.
    • If it's a P1 it should have an assignee.
  • 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.
  • 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.

AMO

Add-ons Manager

Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component

Retrieved from "https://wiki.mozilla.org/index.php?title=Add-ons&oldid=1256248"