Add-ons

The home page for Add-ons at Mozilla.

Including but not limited to:

• Firefox Add-ons
• Firefox for Android Add-ons
• Firefox OS Add-ons
• addons.mozilla.org (AMO)

Our Mission

Add-ons are a safe, simple, and powerful way for people to personalize their web experience.

Who

Engineering

• Andy McKay (internal, blog)
• Stuart Colville (internal, blog, Mozillian Profile)
• Kumar McMillan (internal, blog, Mozillian Profile)
• Mark Striemer (internal)
• Mathieu Agopian (internal, Mozillian Profile)
• Kris Maglione (internal, blog,Mozillian Profile)
• Michael Nolan (internal)
• Matthew McPherson (internal)
• Christopher Grebs (internal)
• Luca Greco (Mozillian Profile)

What time zones are we in?

Looking for the push duty roster maybe?

User Experience

• 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)

Add-ons and Marketplace Management Operations (AMMO team)

• Lisa Brewster, (internal, blog, mozillians profile)
• Amy Tsay, (internal, mozillians profile)
• Jorge Villalobos, (internal, blog, mozillians profile)
• Andreas Wagner, (internal, mozillians profile)
• Andrew Williamson, (internal, mozillians profile)

More info about the AMMO team: https://wiki.mozilla.org/Marketplace/AMMO

QA

• Krupa Raj, (internal, mozillians profile)
• Victor Carciu
• Madalin Cotetiu
• Valentina Peleskei

What

See projects page

See also:

• Extension Signing
• Web Extensions

Getting in touch

• 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
    • Meeting Minutes
• Mailing Lists: dev-addons
• Calendar: Preview, 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:

• 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

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 reports + Meeting Notes

Bi-Weekly Summary of Current Events in Product, Engineering, Community, & UX

• Firefox/AddOns/Status/20150716
• Firefox/AddOns/Status/20150730
• Firefox/AddOns/Status/20150813
• Firefox/AddOns/Status/20150821
• Firefox/AddOns/Status/20150828
• Firefox/AddOns/Status/20150911
• Firefox/AddOns/Status/20150921
• Firefox/AddOns/Status/20150929
• Firefox/AddOns/Status/20151019
• Firefox/AddOns/Status/20151111
• Firefox/AddOns/Status/Updates
• Firefox/AddOns/Status/current

Product Backlog

compiled list of the Add-on repositories, all the work related to the ongoing development and maintenance Add-ons.

• The goals of the Product Backlog are to:
  • 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

• Priorities follow this Standard:
  • Priority 1 - Blocker, must-fix before shipping.
  • Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping.
  • 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.

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

Common Queries

• Webextensions
  • Triaged bugs ***under Toolkit::webextensions in bugzilla
    • have triaged at the end of the Whiteboard
    • blocking-webextensions flag has been set if a milestone 48 target)
  • Untriaged webextension bugs