- 1 What
- 2 Who
- 3 Getting in touch
- 4 Status & Roadmap
- 5 Product Backlog
Mission: Add-ons are a safe, simple, and powerful way for people 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
Looking for 2017 plans?
- Note:* This is a list of people employed by Mozilla. But we are way more than that, please add yourselves in if you want.
- Kumar McMillan (internal, blog, Mozillian Profile)
- Mark Striemer (internal)
- Kris Maglione (internal, blog,Mozillian Profile)
- tofumatt (Matthew Riley MacPherson) (internal)
- Christopher Grebs (internal)
- Luca Greco (Mozillian Profile)
- Andrew Swan (internal)
- Matthew Wein (internal)
- Bob Silverberg (internal)
- Mathieu Pillard (internal])
- Shane Caraveo (internal, Mozillian Profile)
- Andrew Williamson (internal, Mozillian Profile
What time zones are we in?
Looking for the push duty roster maybe?
- Markus Jaritz, UX Designer (internal, Mozillians)
- Blake Winton, UX Engineer (internal, Mozillians)
- Philip Walmsley, Senior Visual Designer (internal)
- more to come as we work on things other than the API...
Program and Product Management
- Kev Needham, Product Manager (internal, blog, mozillians profile)
- Shell Escalante, Program Manager (internal, IRC:shell)
- Jorge Villalobos, (internal, mozillians profile)
- Andreas Wagner, (internal, mozillians profile)
- Philipp Kewisch, (internal, mozillians profile)
Community & Editorial:
- Amy Tsay, (internal, mozillians profile)
- Scott DeVaney (internal, mozillians profile)
- Caitlin Neiman (internal, mozillians profile)
- Krupa Raj, (internal, mozillians profile)
- Victor Carciu
- Madalin Cotetiu
- Valentina Peleskei
- Cosmin Badescu
- Rares Macarie
Getting in touch
- Mailing lists:
- #teamaddons: team chat
- #addons: support for extensions, themes, plugins and addons.mozilla.org
- #amo: addons.mozilla.org bugs and development
- #addon-reviewers add-on reviews and policy (previously #amo-editors)
- #extdev: extension development
- #themedev: theme development
- #webextensions: web extensions
Please see the add-ons Calendar or mailing lists:
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
- Most meetings add their minutes here.
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
Current Status on 5 focus areas
Weekly detailed notes of current event discussions in Product, Engineering, Community, & UX
Roadmap: to the best of our ability, always in progress, so expect changes
For information on the roll out of multi-process Firefox and add-ons, please see the schedule
Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing.
- 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)
- 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 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.
- Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.
- 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.
- 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
- 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.
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component