Add-ons: Difference between revisions
(add link to Projects) |
(Edited the personnel change in developer community from Caitlin to Juhis) |
||
| (24 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
=What= | =What= | ||
'''Mission''': Add-ons | '''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 17: | Line 17: | ||
=== Engineering === | === Engineering === | ||
Engineering | 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]) | |||
* | Engineering Leads: | ||
* | * Shane Caraveo ([https://phonebook.mozilla.org/#search/Shane%20Caraveo internal], [https://mozillians.org/en-US/u/scaraveo/ Mozillian Profile]) | ||
* Mathieu Pillard ([https://phonebook.mozilla.org/#search/Mathieu%20Pillard internal]]) | |||
Engineers: | Engineers: | ||
* William Durand ([https://phonebook.mozilla.org/?search/William%20Durand internal]), [https://mozillians.org/en-US/u/willdurand/ Mozillian Profile] | * 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]) | ||
* | * Tomislav Jovanovic ([https://mozillians.org/en-US/u/zombie/ Mozillian profile]) | ||
* 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]) | * 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] | * 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 === | ||
* | * 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]) | * 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]] === | ||
* | * Rachel Tublitz, Add-ons Lead ([https://people.mozilla.org/p/rachel internal]) | ||
* Jorge Villalobos, Product Manager ([https://phonebook.mozilla.org/#search/jorge internal], [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]) | ||
* Scott DeVaney, Sr. Editorial Manager ([https://phonebook.mozilla.org/#search/devaney internal], [https://mozillians.org/en-US/u/sdevaney/ mozillians profile]) | |||
* Juha-Matti Santala, Developer Advocate ([https://people.mozilla.org/p/juhis internal]) | |||
* Scott DeVaney, Editorial | * 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]) | ||
* Andreas Wagner, | |||
* Philipp Kewisch, | |||
=== QA === | === QA === | ||
| Line 72: | Line 58: | ||
=Get in touch= | =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. | |||
===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]]: | ||
* | ** 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/ | |||
== Meetings == | == Meetings == | ||
Please see the add-ons | Please see the add-ons calendar: | ||
* 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] | ||
Minutes: | Minutes: | ||
Click into the calendar event to find links to publicly available meeting minutes. | |||
===Contribute to Add-ons=== | ===Contribute to Add-ons=== | ||
| Line 109: | Line 89: | ||
=Status & Roadmap= | =Status & Roadmap= | ||
Bugs are stored in one of two places depending upon the project. Roadmaps are all stored in Trello. | Bugs are stored in one of two places depending upon the project. Roadmaps are all stored in Trello. | ||
| Line 120: | Line 98: | ||
Bugs: | 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 == | == Github == | ||
| Line 136: | Line 114: | ||
We use Trello for planning out roadmaps. A Trello card normally relates to multiple bugs, or a larger feature. | 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] | |||
* [https://trello.com/b/PC9kB14s/ | |||
== Multi-process Firefox == | == Multi-process Firefox == | ||
| Line 205: | Line 181: | ||
*[http://mzl.la/1T6QAeZ Untriaged bugs within past 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:
- Firefox Add-ons
- Firefox for Android Add-ons
- addons.mozilla.org (AMO)
- Extension Signing
- WebExtensions
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:
- Stuart Colville (internal, blog, Mozillian Profile)
Engineering Leads:
- Shane Caraveo (internal, Mozillian Profile)
- Mathieu Pillard (internal])
Engineers:
- William Durand (internal), Mozillian Profile
- Luca Greco (Mozillian Profile)
- Tomislav Jovanovic (Mozillian profile)
- Bob Silverberg (internal)
- Andrew Williamson (internal, Mozillian Profile)
- Rob Wu (internal, Mozillian Profile)
Looking for the push duty roster maybe?
User Experience
- Aaron Benson, UX Designer (internal)
Partial support:
- Emanuela Damiani, UX Designer (internal)
Product Management and Community Experience
- Rachel Tublitz, Add-ons Lead (internal)
- Jorge Villalobos, Product Manager (internal, mozillians profile)
- Scott DeVaney, Sr. Editorial Manager (internal, mozillians profile)
- Juha-Matti Santala, Developer Advocate (internal)
- Andreas Wagner, Product Operations Manager (internal, mozillians profile)
- Philipp Kewisch, Operations Manager (internal, mozillians profile)
QA
- Krupa Raj (internal, mozillians profile)
- Victor Carciu
- Madalin Cotetiu
- 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 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
- 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/
Meetings
Please see the add-ons calendar:
- Calendar: Preview, iCal import
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.
- See how you can help: https://wiki.mozilla.org/Add-ons/Contribute
- Subscribe to the 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
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:
- under WebExtensions: (various components)
- under Toolkit: Add-ons Manager
- under Firefox for Android: Add-on Manager
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
- Experimenting with new triage process, will change as needed
- Triage Query
Add-ons Manager
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component
- Untriaged bugs within past 120 days
- follow bugzilla triage guidelines, process always open to change
- Triaged bugs have triaged tag added to end of whiteboard or have a Priority set.