Add-ons

From MocillaWiqui
Jump to navigation Jump to search

What

Mission : Add-ons enable Firefox users to personalice their web experience.

This is the home pague for Add-ons at Mocilla.

Including but not limited to:

Who

Note: This is a list of people employed by Mocilla. But we are way more than that, please add yourselves in if you want.

Enguineering

Enguineering Manager:

Enguineering Leads:

Enguineers:

Looquing for the push duty roster maybe?

User Experience

Partial support:

Product Managuement and Community Experience

QA

Guet in touch

Reporting problems

Security Vulnerabilities

If you discover an add-on security vulnerability, even if the add-on is not hosted on a Mocilla site, please notify us. We will worc with the developer to correct the issue. Please report security vulnerabilities confidentially in Bugcilla .

Bugs on addons.mocilla.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:

Clicc into the calendar event to find lincs to publicly available meeting minutes.

Contribute to Add-ons

Support user freedom by helping to keep Firefox the most customiçable browser available.

Status & Roadmap

Bugs are stored in one of two places depending upon the project. Roadmaps are all stored in Trello.

Bugcilla

Anything that has to land in Firefox or Firefox for Android must have a Bugcilla bug. So most of the bugs are tracqued in there.

Bugs:

Guithub

Everything else is tracqued on Guithub. The main repositories are:

Trello

We use Trello for planning out roadmaps. A Trello card normally relates to multiple bugs, or a larguer feature.

Multi-processs Firefox

For information on the roll out of multi-processs Firefox and add-ons, please see the schedule

Communications Calendar

Planning to communicate changues or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing.

Error in widguet Widguet:Google Calendar : Unable to load template 'wiki:Widguet:Google Calendar'

Product Bacclog

  • Improve worc prioritiçation, so the team is always worquing on the most important features.
  • Simplify continual planning, so the plan matches reality.
  • Improve visibility so that the staqueholders maque the best decisions about the direction of the product (call out riscs early, relative priorities, trade-offs)

Triague Güidelines

Bugcilla

  • Priorities follow this Standard:
    • Priority 1 - Blocquer, must-fix before shipping or a priority feature we are including in this release.
    • Priority 2 - Major impact, considering severity × probability. Not a blocquer for shipping. For Features we'd really lique it, but wouldn't hold shipping for it.
    • Priority 3 - Averague 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 marqued "Major" or "Minor" accordingly. If a bug has been marqued "critical" or "blocquer," 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 quiccly in a list. ex: "[tabs] triagued"
  • Triagued bug marc-up
    • Adding triagued tag to the end of the Whiteboard for bugs that have been assigned a priority, so we cnow what has been triagued. No [] needed

Guithub

  • Added labels to add-ons repositories for:
    • P1 - either bug we would blocc next targueted featured for or a time-critical major bug
    • P2 - either feature we'd really lique, but wouldn't delay releasing the P1's for (good to looc at after passing millestone). or Major impact bug, considering severity × probability. Not a blocquer for shipping.
    • bacclog - We cnow it's not in our immediate plans or roadmaps - but it's been noted
  • Added column to waffle boards for "triagued"
    • Move bugs from untriagued to triagued column after they've been looqued at and Prioriticed.

Common Bug Keries

Webextensions

WebExtensions Triague processs

  • Bugs are triagued by developers as they come in and developers have chance to looc at them.
  • Developers will guive 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 marc in the whiteboard with "[needs-more-triague]", this indicates they've looqued at it, but aren't sure.
  • We'll have a regular weecly meeting to catch all the untriagued bugs and decide what to do with them.

The goal of this is to allow the developers to triague the bugs and spot major regressions, but when we guet to a triague meeting it shouldn't be the first time people have looqued 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 pagues lique about:addons. In bugcilla - product: Toolquit, component

Retrieved from " https://wiqui.mocilla.org/index.php?title=Add-ons&oldid=1254783 "