Add-ons: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (added communications calendar)
(Updated list of peoples, removed reference to defunct phonebook and mozillians site, remove some obsolete sections, update some links)
 
(126 intermediate revisions by 22 users not shown)
Line 1: Line 1:
The home page for Add-ons at Mozilla.
=What=
 
'''Mission''': Add-ons enable Firefox users to personalize their web experience.
<p></p>
This is the home page for Add-ons at Mozilla.
<p></p>
Including but not limited to:
Including but not limited to:
* Firefox Add-ons
* Firefox Add-ons
* Firefox for Android Add-ons
* Firefox for Android Add-ons
* [https://developer.mozilla.org/Firefox_OS/Add-ons Firefox OS Add-ons]
* [https://addons.mozilla.org/firefox/ addons.mozilla.org (AMO)]
* [https://addons.mozilla.org/firefox/ addons.mozilla.org (AMO)]
* [[Add-ons/Extension_Signing|Extension Signing]]
* [[WebExtensions|WebExtensions]]
=Who=


== 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 ===


* Andy McKay ([https://phonebook.mozilla.org/#search/Andy%20McKay internal], [http://mckay.pub blog])
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)
* Kumar McMillan ([https://phonebook.mozilla.org/#search/Kumar%20McMillan internal], [http://farmdev.com/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])
 
* Mark Striemer ([https://phonebook.mozilla.org/#search/Mark%20Striemer internal])
Engineering Leads:
* Mathieu Agopian ([https://phonebook.mozilla.org/#search/Mathieu%20Agopian internal], [https://mozillians.org/en-US/u/magopian/ Mozillian Profile])
* William Durand (:willdurand)
* Kris Maglione ([https://phonebook.mozilla.org/#search/kris%20m internal], [http://blog.5digits.org/ blog],[https://mozillians.org/en-US/u/John-Galt/ Mozillian Profile])
* Mathieu Pillard
* Michael Nolan ([https://phonebook.mozilla.org/#search/Michael%20Nolan internal])
 
* Matthew McPherson ([https://phonebook.mozilla.org/#search/Matthew%20McPherson internal])
Engineers:
* Christopher Grebs ([https://phonebook.mozilla.org/#search/Christopher%20Grebs internal])
* Luca Greco (:rpl)
* Luca Greco ([https://mozillians.org/en-US/u/luca/ Mozillian Profile])
* Tomislav Jovanovic (:zombie)
* Andrew Williamson
* Rob Wu (:robwu)
 
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=


What [http://www.timeanddate.com/worldclock/meetingtime.html?p1=256&p2=136&p3=64&p4=195&p5=265&p6=202 time zones are we in]?
==Reporting problems==


Looking for the [http://addons.readthedocs.org/en/latest/server/push-duty.html push duty roster] maybe?
===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].


=== User Experience ===
===Bugs on addons.mozilla.org===
* Markus Jaritz, UX Designer ([https://phonebook.mozilla.org/tree.php#search/markus@mozilla.com internal], [https://mozillians.org/en-US/u/mjaritz/ Mozillians])
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.
* Blake Winton, UX Engineer ([https://phonebook.mozilla.org/tree.php#search/bwinton@mozilla.com internal], [https://mozillians.org/en-US/u/bwinton/ Mozillians])
* ''more to come as we work on things other than the API...''


=== Program and Product Management ===
==Contact us==
* Kev Needham, Product Manager ([https://phonebook.mozilla.org/tree.php#search/kneedham@mozilla.com internal], [http://kev.deadsquid.com/ blog], [https://mozillians.org/en-US/u/kev/ mozillians profile])
* [[Matrix]]:
* Shell Escalante, Program Manager ([https://phonebook.mozilla.org/#search/shell@mozilla.com internal])
** Add-ons:  support for extensions, themes, and API development
** Add-on Reviewers: add-on reviews and policy
** AMO: addons.mozilla.org bugs and development
* Community Forum: https://discourse.mozilla.org/c/add-ons/
* Blog: https://blog.mozilla.org/addons/


=== Add-ons and Marketplace Management Operations (AMMO team) ===
== Meetings ==
* Lisa Brewster, ([https://phonebook.mozilla.org/#search/brewster internal], [http://www.adora.io/ blog], [https://mozillians.org/en-US/u/Adora/ mozillians profile])
* Amy Tsay, ([https://phonebook.mozilla.org/#search/tsay internal], [https://mozillians.org/en-US/u/amyt/ mozillians profile])
* Jorge Villalobos, ([https://phonebook.mozilla.org/#search/jorge internal], [http://xulforge.com/blog/ blog], [https://mozillians.org/en-US/u/jorgev/ mozillians profile])
* Andreas Wagner, ([https://phonebook.mozilla.org/#search/andreas%20wagner internal], [https://mozillians.org/en-US/u/TheOne/ mozillians profile])
* Andrew Williamson, ([https://phonebook.mozilla.org/#search/andrew%20williamson internal], [https://mozillians.org/en-US/u/eviljeff/ mozillians profile])


More info about the AMMO team:  https://wiki.mozilla.org/Marketplace/AMMO
From 2025 until 2018, the add-ons team held regular public meetings, with meeting notes archived at [[Add-ons/Contribute/Triage]].


=== QA ===
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].
* Krupa Raj, ([https://phonebook.mozilla.org/#search/krupa internal], [https://mozillians.org/en-US/u/kruparaj/ mozillians profile])
* Victor Carciu
* Madalin Cotetiu
* Valentina Peleskei


== What ==
===Contribute to Add-ons===
Support user freedom by helping to keep Firefox the most customizable browser available.
*See how you can help: https://wiki.mozilla.org/Add-ons/Contribute
*Subscribe to the [https://discourse.mozilla.org/c/add-ons/contribute Add-ons Contribution] forum to be kept in the loop about contribution opportunities and events. Click on the menu at the top-right corner of the page and select "Watching".


[[Add-ons/Projects|See projects page]]
=Status & Roadmap=


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


* [[Add-ons/Extension_Signing|Extension Signing]]
== Bugzilla ==
* [[WebExtensions|Web Extensions]]
 
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:
 
* under [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=WebExtensions WebExtensions: (various components)]
* under [https://bugzilla.mozilla.org/buglist.cgi?list_id=13815989&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Add-ons%20Manager&product=Toolkit Toolkit: Add-ons Manager]
* under [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Add-on%20Manager&product=Firefox%20for%20Android Firefox for Android: Add-on Manager]
 
== Github ==


== Getting in touch ==
Everything else is tracked on Github. The main repositories are:
* [[IRC|IRC]]:
** #teamaddons: team chat
** #addons:  support for extensions, themes, plugins and addons.mozilla.org
** #amo: addons.mozilla.org bugs and development
** #amo-editors: add-on reviews and policy
** #extdev: extension development
** #themedev: theme development
** #webextensions: web extensions
* Meetings:
** Tuesday Bi-Weekly Extended Team Meeting
*** 10am PST/18:00 UTC/13:00 EST
*** Add-ons Vidyo Room
*** [https://wiki.mozilla.org/Add-ons/Bi-weekly-minutes Meeting Minutes]
* Mailing Lists: [https://mail.mozilla.org/listinfo/dev-addons dev-addons]
* 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]
* Blog: https://blog.mozilla.org/addons/
* Forum: https://discourse.mozilla-community.org/c/add-ons


Most meetings are in the Add-ons Vidyo room. To access remotely:
* [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]


* Using Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=gBI6Q6943nQv 
== Multi-process Firefox ==
* To join from a telephone: US Toll Free +1 800 707 2533, pin 369, conf 98839


== Contribute to Add-ons ==
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]
Support user freedom by helping to keep Firefox the most customizable browser available.
*See how you can help: https://wiki.mozilla.org/Add-ons/Contribute
*Subscribe to the [https://discourse.mozilla-community.org/c/add-ons/contribute Add-ons Contribution] forum to be kept in the loop about contribution opportunities and events. Click on the menu at the top-right corner of the page and select "Watching".


== Status reports + Meeting Notes ==
===Communications Calendar===
[https://docs.google.com/document/d/17o2l7VV9OBwXxGeEUQf0-4dZhlbbrJPkGbIXA-ht2Tg/edit# Bi-Weekly Summary of Current Events in Product, Engineering, Community, & UX]
Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing.
{{Special:PrefixIndex/Firefox/AddOns/Status/}}


=Add-ons Communication Calendar=
{{#widget:Widget:Google Calendar
{{#widget:Widget:Google Calendar
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
Line 98: Line 101:


=Product Backlog=
=Product Backlog=
[http://addons.readthedocs.org/en/latest/repositories.html '''compiled list'''] of the Add-on repositories, all the work related to the ongoing development and maintenance Add-ons.
* Improve work prioritization, so the team is always working on the most important features.
*The goals of the Product Backlog are to:
* Simplify continual planning, so the plan matches reality.
** Improve work prioritization, so the team is always working on the most important features.
* Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs)
** 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)
<p> </p>
<p> </p>


==Triage Guidelines==
==Triage Guidelines==
===Bugzilla===
* '''Priorities''' follow this Standard:
* '''Priorities''' follow this Standard:
** Priority 1 - Blocker, must-fix before shipping.  
** 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.
** 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 3 - Average Bug.  definitely a problem, but doesn't stop someone from using the product.  
** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.
** Priority 4 - Not used.
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.
** Priority 5 - Low-impact. Something we won't fix, but would accept patches for.
<p> </p>
<p> </p>
*'''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.
*'''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.
<p> </p>
<p> </p>
*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
*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.
**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
**Adding a '''short descriptive area tag''' in the whiteboard when possible, to visually group bugs quickly in a list
 
** Webextensions: The '''blocking-webextensions''' flag is used to track bugs that are aiming for '''milestone 48'''
===Github===
*Added labels to [https://mozilla.github.io/addons/repositories.html 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==
===[https://wiki.mozilla.org/WebExtensions#Useful_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.
* [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.
 
===AMO===
*Experimenting with [https://wiki.mozilla.org/Add-ons#Github new triage process], will change as needed


==Common Queries==
===Add-ons Manager===
*Webextensions
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component
**[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12810463&o1=substring&resolution=---&query_format=advanced&v1=triaged&component=WebExtensions&product=Toolkit Triaged bugs] ***under Toolkit::webextensions in bugzilla
*[http://mzl.la/1T6QAeZ Untriaged bugs within past 120 days]
***have '''triaged''' at the end of the Whiteboard
**follow [https://wiki.mozilla.org/Add-ons#Bugzilla bugzilla triage guidelines], process always open to change
***'''blocking-webextensions''' flag has been set if a milestone 48 target)
*[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12941866&o1=substring&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=triaged&component=Add-ons%20Manager&product=Toolkit Triaged bugs] have '''triaged''' tag added to end of '''whiteboard''' or have a Priority set.
**[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12810465&o1=notsubstring&resolution=---&query_format=advanced&v1=triaged&component=WebExtensions&product=Toolkit Untriaged webextension bugs]

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"