Add-ons

From MozillaWiki
Jump to: navigation, search

What

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:

Looking for 2017 plans?

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 Managers:

Engineers:

What time zones are we in?

Looking for the push duty roster maybe?

User Experience

Program and Product Management

Add-on Community Experience (ACE team)

Developer Experience:

Community & Editorial:

QA

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

Please see the add-ons Calendar or mailing lists:

Most meetings are in the Add-ons Vidyo room. To access remotely:

Minutes:

Contribute to Add-ons

Support user freedom by helping to keep Firefox the most customizable browser available.

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

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.

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

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 Queries

Webextensions

AMO

Add-ons Manager

Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component