Features/Desktop/Improve Add-on Monitoring

Status

Team

Open issues/risks

Many of these features would require work on AMO. Most AMO developer focus these days is directed to the new Marketplace, so we might need help.

Stage 1: Definition

1. Feature overview

We want to have a way to better control add-ons that are distributed outside of AMO, while preserving add-on developers' freedom to create and distribute their work.

This is a system that would require add-on developers to upload their add-on files to AMO for registration. Uploaded files would be tied to a developer account and would only go through automated code tests before being accepted. Unregistered files would then become much more difficult to install, requiring add-ons to be whitelisted by the user.

2. Users & use cases

This is meant to protect end users from spontaneous malware. It will also give the Add-ons Team greater insight into unknown add-ons and common add-on malware patterns.

3. Dependencies

`

4. Requirements

Current PRD

See also Add-on File Registration

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`

Feature details

Team status notes