Add-ons: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
(Updated list of peoples, removed reference to defunct phonebook and mozillians site, remove some obsolete sections, update some links)
 
(168 intermediate revisions by 26 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
* Firefox OS Add-ons
* [https://addons.mozilla.org/firefox/ addons.mozilla.org (AMO)]
* 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:
* Luca Greco (:rpl)
* Tomislav Jovanovic (:zombie)
* Andrew Williamson
* Rob Wu (:robwu)


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]?
Looking for the [https://mozilla.github.io/addons/server/push-duty.html push duty roster] maybe?


=== Program and Product Management ===
=== Product Management and [[Add-ons/ACE|Community Experience]] ===
* 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])
* Scott DeVaney, Sr. Editorial Manager
* Larissa Shapiro, Program Manager ([https://phonebook.mozilla.org/#search/lshapiro@mozilla.com internal], [https://contentsmayvary.blogspot.com blog], [https://mozillians.org/en-US/u/lshapiro/ mozillians profile])
* Andreas Wagner, Product Operations Manager
* Abhishek Nagekar, Add-ons Security Engineer


=== Add-ons and Marketplace Management Operations (AMMO team) ===
=Get in touch=
* 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
==Reporting problems==


== What ==
===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].


Each iteration (or milestone) is two weeks long, giving three milestones per Firefox train.
===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.


=== Iteration 44.1 ===
==Contact us==
* [[Matrix]]:
** 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/


==== JS Validator ====
== Meetings ==
* Who: Stuart, Tofumatt
* What: porting validator to JS (see [https://github.com/mozilla/addons-validator||github])
* Tracker: [https://waffle.io/mozilla/addons?source=mozilla%2Faddons-validator|Github issues via Waffle]
* Status: <span style="color:green; font-weight:bold">In discovery</span>


==== Metrics ====
From 2025 until 2018, the add-ons team held regular public meetings, with meeting notes archived at [[Add-ons/Contribute/Triage]].
* Who: Kumar
* What: get a basic dashboard of metrics for AMO using graphite to give us visibility into the review queues
* Tracker:
* Status: <span style="color:green; font-weight:bold">In discovery</span>


==== Signing ====
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].
* Who: Magopian, Mark, Michael
* What: helping getting signing out the door, validator queues improvements, signing API
* Tracker: {{Bugzilla|1070153}}, {{Bugzilla|1206158}}
* Status: <span style="color:green; font-weight:bold">On schedule</span>


=== Iteration 44.2 ===
===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".


==== Web Extensions ====
=Status & Roadmap=
* Who: Kris
* What:
* Tracker:
* Status:


=== Overall ===
Bugs are stored in one of two places depending upon the project. Roadmaps are all stored in Trello.
* [https://wiki.mozilla.org/Addons/Extension_Signing Add-Ons Signing]
* [https://wiki.mozilla.org/WebExtensions Web Extensions]


== Getting in touch ==
== Bugzilla ==
* [[IRC|IRC]]: #addons, #amo
 
* Meetings:
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.
* Mailing Lists:
 
* Calendar: https://www.google.com/calendar/render?mode=day&date=20150916T175044
Bugs:
* Blog: https://blog.mozilla.org/addons/
 
* Forum: https://discourse.mozilla-community.org/c/add-ons
* 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 ==
 
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]
 
== 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 [https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule the schedule]
 
===Communications Calendar===
Planning to communicate changes or coming features.  One example is blogs, audiences, channels, and who will be writing/reviewing.
 
{{#widget:Widget:Google Calendar
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
}}
 
=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.
<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. If a bug has been marked "critical" or "blocker," that bug should be made a P1.
<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
**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 [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===


== Status reports ==
* 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]


{{Special:PrefixIndex/Firefox/AddOns/Status/}}
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.


== Current Work ==
===AMO===
=== Themes ===
*Experimenting with [https://wiki.mozilla.org/Add-ons#Github new triage process], will change as needed
Current themes being worked on.


=== Iterations ===
===Add-ons Manager===
We work in two week iterations, three iterations per Firefox release. Current iterations work is described here.
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component
*[http://mzl.la/1T6QAeZ Untriaged bugs within past 120 days]
**follow [https://wiki.mozilla.org/Add-ons#Bugzilla bugzilla triage guidelines], process always open to change
*[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.

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"