Features/Desktop/Improve Add-on Monitoring
Status
| Improve Add-on Monitoring | |
| Stage | Draft |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Improve Add-on Monitoring
|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | Jorge Villalobos |
| Lead engineer | Blair McBride |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | Matt Grimes, Tyler Downer, Michael Verdi |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=Jorge Villalobos |Feature lead engineer=Blair McBride |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Matt Grimes, Tyler Downer, Michael Verdi }}
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
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
` {{#set:Feature open issues and 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. |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. |Feature users and 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. |Feature dependencies=` |Feature requirements=Current PRD
See also Add-on File Registration |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}