Features/Desktop/Enhanced Blocklisting
From MozillaWiki
Please use "Edit with form" above to edit this page.
Status
| Enhanced Blocklisting | |
| Stage | Draft |
| Status | ` |
| Release target | ` |
| Health | OK |
| 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 |
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
The add-ons blocklist was designed as an emergency mechanism for clearly malicious add-ons. We now require a smarter blocklisting system that allows us to warn users about non-malicious add-ons that are problematic, and also perform cleanup tasks like reverting setting changes.
- bug ? - Increase blocklist refresh rate to twice a day.
- bug ? - Make Add-ons Manager look for suitable upgrades or downgrades before issuing a block.
- bug ? - Expand blocklist features.
- Support warnings for policy violations and performance problems.
- Support reverting settings (homepage, default search, keyword URL).
- Support custom URLs (SUMO pages, blog posts).
- Support add-on install reminder (like the Firefox 8 opt-in).
See also Blocklist Wishlist.
2. Users & use cases
This is aimed at end users, mainly when they install a malicious or misbehaving add-on. We want to have more flexibility when issuing blocks.
3. Dependencies
`
4. Requirements
`
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
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
