Add-ons: Difference between revisions

(Edited the personnel change in developer community from Caitlin to Juhis)
 
(72 intermediate revisions by 17 users not shown)
Line 1: Line 1:
=What=
=What=
'''Mission''': Add-ons are a safe, simple, and powerful way for people to personalize their web experience.
'''Mission''': Add-ons enable Firefox users to personalize their web experience.
<p></p>
<p></p>
This is the home page for Add-ons at Mozilla.
This is the home page for Add-ons at Mozilla.
Line 7: Line 7:
* 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/Projects|See projects page]]
* [[Add-ons/Extension_Signing|Extension Signing]]
* [[Add-ons/Extension_Signing|Extension Signing]]
* [[WebExtensions|Web Extensions]]
* [[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.
'''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], [https://mozillians.org/en-US/u/andym/ Mozillian profile])
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])
* Stuart Colville ([https://phonebook.mozilla.org/#search/Stuart%20Colville internal], [https://muffinresearch.co.uk/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])
* 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])
* Shane Caraveo ([https://phonebook.mozilla.org/#search/Shane%20Caraveo internal], [https://mozillians.org/en-US/u/scaraveo/ Mozillian Profile])
* 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 ([https://phonebook.mozilla.org/#search/Mathieu%20Pillard internal]])
* Matthew McPherson ([https://phonebook.mozilla.org/#search/Matthew%20McPherson internal])
 
* Christopher Grebs ([https://phonebook.mozilla.org/#search/Christopher%20Grebs internal])
Engineers:
* William Durand ([https://phonebook.mozilla.org/?search/William%20Durand internal]), [https://mozillians.org/en-US/u/willdurand/ Mozillian Profile]
* Luca Greco ([https://mozillians.org/en-US/u/luca/ Mozillian Profile])
* Luca Greco ([https://mozillians.org/en-US/u/luca/ Mozillian Profile])
* Andrew Swan ([https://phonebook.mozilla.org/#search/Andrew%20Swan internal])
* Tomislav Jovanovic ([https://mozillians.org/en-US/u/zombie/ Mozillian profile])
* Matthew Wein ([https://phonebook.mozilla.org/#search/Matthew%20Wein internal])
* Bob Silverberg ([https://phonebook.mozilla.org/#search/Bob%20Silverberg internal])
* Bob Silverberg ([https://phonebook.mozilla.org/#search/Bob%20Silverberg internal])
 
* Andrew Williamson ([https://phonebook.mozilla.org/?search/eviljeff internal], [https://mozillians.org/en-US/u/eviljeff/ Mozillian Profile])
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]?
* 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 [http://addons.readthedocs.org/en/latest/server/push-duty.html push duty roster] maybe?


=== User Experience ===
=== User Experience ===
* Markus Jaritz, UX Designer ([https://phonebook.mozilla.org/tree.php#search/markus@mozilla.com internal], [https://mozillians.org/en-US/u/mjaritz/ Mozillians])
* Aaron Benson, UX Designer ([https://people.mozilla.org/p/r--M7dY4lqwUiuGc4Hnliswdg== internal])
* Blake Winton, UX Engineer ([https://phonebook.mozilla.org/tree.php#search/bwinton@mozilla.com internal], [https://mozillians.org/en-US/u/bwinton/ Mozillians])
* Philip Walmsley, Senior Visual Designer ([https://phonebook.mozilla.org/search.php?format=vcard&query=pwalmsley@mozilla.com internal])
* ''more to come as we work on things other than the API...''


=== Program and Product Management ===
Partial support:
* 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])
* Emanuela Damiani, UX Designer ([https://phonebook.mozilla.org/?search/emanuela internal])
* Shell Escalante, Program Manager ([https://phonebook.mozilla.org/#search/shell@mozilla.com internal], IRC:shell)


=== [[Add-ons/ACE|Add-on Community Experience (ACE team)]] ===
=== Product Management and [[Add-ons/ACE|Community Experience]] ===
Developer Experience:
* Rachel Tublitz, Add-ons Lead ([https://people.mozilla.org/p/rachel internal])
* Jorge Villalobos, ([https://phonebook.mozilla.org/#search/jorge internal], [http://xulforge.com/blog/ blog], [https://mozillians.org/en-US/u/jorgev/ mozillians profile])
* Jorge Villalobos, Product Manager ([https://phonebook.mozilla.org/#search/jorge internal], [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])
* Scott DeVaney, Sr. Editorial Manager ([https://phonebook.mozilla.org/#search/devaney internal], [https://mozillians.org/en-US/u/sdevaney/ mozillians profile])
* Andrew Williamson, ([https://phonebook.mozilla.org/#search/andrew%20williamson internal], [https://mozillians.org/en-US/u/eviljeff/ mozillians profile])
* Juha-Matti Santala, Developer Advocate ([https://people.mozilla.org/p/juhis internal])
* Philipp Kewisch, ([https://phonebook.mozilla.org/#search/kewisch internal], [https://mozillians.org/en-US/u/kewisch/ mozillians profile])
* Andreas Wagner, Product Operations Manager ([https://phonebook.mozilla.org/#search/andreas%20wagner internal], [https://mozillians.org/en-US/u/TheOne/ mozillians profile])
 
* Philipp Kewisch, Operations Manager ([https://phonebook.mozilla.org/#search/kewisch internal], [https://mozillians.org/en-US/u/kewisch/ mozillians profile])
Community & Editorial:
* Amy Tsay, ([https://phonebook.mozilla.org/#search/tsay internal], [https://mozillians.org/en-US/u/amyt/ mozillians profile])
* Scott DeVaney ([https://phonebook.mozilla.org/#search/devaney internal], [https://mozillians.org/en-US/u/sdevaney/ mozillians profile])


=== QA ===
=== QA ===
* Krupa Raj, ([https://phonebook.mozilla.org/#search/krupa internal], [https://mozillians.org/en-US/u/kruparaj/ mozillians profile])
* Krupa Raj ([https://phonebook.mozilla.org/#search/krupa internal], [https://mozillians.org/en-US/u/kruparaj/ mozillians profile])
* Victor Carciu
* Victor Carciu
* Madalin Cotetiu
* Madalin Cotetiu
* Valentina Peleskei
* Valentina Peleskei
* Cosmin Badescu
* Rares Macarie
=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] or by emailing amo-admins@mozilla.com.


=Getting in touch=
===Bugs on addons.mozilla.org===
* [[IRC|IRC]]:
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.
** #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


==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/
* Blog: https://blog.mozilla.org/addons/
* Forum: https://discourse.mozilla-community.org/c/add-ons


== Meetings ==
== Meetings ==


Please see the add-ons Calendar or mailing lists:
Please see the add-ons calendar:
 
* 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]
* 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]
Most meetings are in the Add-ons Vidyo room. To access remotely:
* Using Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=gBI6Q6943nQv 
* To join from a telephone: US Toll Free +1 800 707 2533, pin 369, conf 98839


Minutes:
Minutes:


* Most meetings [https://docs.google.com/document/d/1oNq9vZCNgMUnjJ0prfeWzudibtMwkCoNfVxN3a7j90A/edit add their minutes here].
Click into the calendar event to find links to publicly available meeting minutes.  


===Contribute to Add-ons===
===Contribute to Add-ons===
Support user freedom by helping to keep Firefox the most customizable browser available.
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
*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".
*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".


=Status & Roadmap=
=Status & Roadmap=
[https://wiki.mozilla.org/Firefox/AddOns/Status/current Current Status] on 5 focus areas
 
<p></p>
Bugs are stored in one of two places depending upon the project. Roadmaps are all stored in Trello.
[https://docs.google.com/document/d/17o2l7VV9OBwXxGeEUQf0-4dZhlbbrJPkGbIXA-ht2Tg/edit# Weekly detailed notes] of current event discussions in Product, Engineering, Community, & UX
 
<p></p>
== Bugzilla ==
[https://mozilla.aha.io/published/0d49e74c6853d3d721010bd9d4f67f34?page=1 Roadmap]: to the best of our ability, always in progress, so expect changes
 
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 ==
 
Everything else is tracked on Github. The main repositories are:
 
* [http://github.com/mozilla/addons-server addons server]
* [http://github.com/mozilla/addons-frontend addons frontend]
* [http://github.com/mozilla/addons-linter addons linter]
 
== 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 ==
 
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]


===Communications Calendar===
===Communications Calendar===
Line 125: Line 141:
** 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 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'''
*Optional '''Whiteboard tag'''
Line 137: Line 153:
===Github===
===Github===
<p> </p>
<p> </p>
*Added labels to [add-ons http://addons.readthedocs.org/en/latest/repositories.html 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 144: Line 160:
**Move bugs from '''untriaged''' to '''triaged''' column after they've been looked at and Prioritized.
**Move bugs from '''untriaged''' to '''triaged''' column after they've been looked at and Prioritized.


==Common Queries==
==Common Bug Queries==
===Webextensions===
===[https://wiki.mozilla.org/WebExtensions#Useful_queries Webextensions]===
Bugs under Toolkit::webextensions in bugzilla and in github with label=[https://waffle.io/mozilla/addons?label=WebExtensions WebExtensions]
 
*[https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=12875291&o1=notsubstring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=blocking-webextensions&component=WebExtensions&v2=triaged&product=Toolkit Untriaged webextension bugs] (no '''triaged''' whiteboard tag)
===WebExtensions Triage process===
**follow [https://wiki.mozilla.org/Add-ons#Bugzilla bugzilla triage guidelines], process always open to streamlining
 
**'''blocking-webextensions''' flag is used to track bugs for the next major milestone.  Can leave blank, unless you want it considered then either set to '''?''' or '''+''' (if you want to approve in one step during triage).
* Bugs are triaged by developers as they come in and developers have chance to look at them.
*[https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&o1=anywordssubstr&resolution=---&query_format=advanced&v1=blocking-webextensions%3F&component=WebExtensions&product=Toolkit&list_id=12941362 Blocking-webextensions ?]
* Developers will give the bug a priority (P1,2,3 or 5) and move to the appropriate component.
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&chfieldto=Now&query_format=advanced&chfield=cf_last_resolved&chfieldfrom=-17d&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&component=WebExtensions&product=Toolkit&list_id=12941356 Closed in last 17 days]
** If it's a P1 it should have an assignee.
*[https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&o1=anywords&resolution=---&query_format=advanced&v1=blocking-webextensions%2B&list_id=12737558 web extensions target for milestone 48]
* 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.
*[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] have '''triaged''' at the end of the Whiteboard notes
* We'll have a regular weekly meeting to catch all the untriaged bugs and decide what to do with them.
 
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===
===AMO===
Line 161: Line 179:
===Add-ons Manager===
===Add-ons Manager===
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component
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=12967324&o1=notsubstring&resolution=---&chfieldto=Now&query_format=advanced&chfield=[Bug%20creation]&chfieldfrom=-120d&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=triaged&component=Add-ons%20Manager&product=Toolkit] and created in last 120 days
*[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
**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'''
*[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 10:42, 28 October 2022

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:

Engineering Leads:

Engineers:

Looking for the push duty roster maybe?

User Experience

Partial support:

  • Emanuela Damiani, UX Designer (internal)

Product Management and Community Experience

QA

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 or by emailing amo-admins@mozilla.com.

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

Please see the add-ons calendar:

Minutes:

Click into the calendar event to find links to publicly available meeting 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:

Trello

We use Trello for planning out roadmaps. A Trello card normally relates to multiple bugs, or a larger feature.

Multi-process Firefox

For information on the roll out of multi-process Firefox and add-ons, 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.

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