Features/Desktop/Enhanced Blocklisting

Please use "Edit with form" above to edit this page.

Status

Enhanced Blocklisting
Stage	Draft
Status	`
Release target	`
Health	OK
Status note	`

{{#set:Feature name=Enhanced Blocklisting

|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

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

` {{#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=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. |Feature users and 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. |Feature dependencies=` |Feature requirements=` |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=` }}