Add-ons: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(fixed internal link)
(test)
Line 134: Line 134:
***'''blocking-webextensions''' flag has been set if a milestone 48 target)
***'''blocking-webextensions''' flag has been set if a milestone 48 target)
**[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12810465&o1=notsubstring&resolution=---&query_format=advanced&v1=triaged&component=WebExtensions&product=Toolkit Untriaged webextension bugs]
**[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12810465&o1=notsubstring&resolution=---&query_format=advanced&v1=triaged&component=WebExtensions&product=Toolkit Untriaged webextension bugs]
{{Special:PrefixIndex/Firefox/AddOns/Status/}}

Revision as of 17:18, 29 January 2016

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:

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

What time zones are we in?

Looking for the push duty roster maybe?

User Experience

Program and Product Management

Add-ons and Marketplace Management Operations (AMMO team)

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

QA

Getting in touch

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

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

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

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
Retrieved from "https://wiki.mozilla.org/index.php?title=Add-ons&oldid=1114947"