Add-ons

From MozillaWiki
(Redirected from AMO)
Jump to: navigation, search

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.

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

Retrieved from "https://wiki.mozilla.org/index.php?title=Add-ons&oldid=1251174"