Features/Desktop/Add-on hotfix

From MozillaWiki
< Features‎ | Desktop
Revision as of 20:31, 3 October 2011 by Clegnitto (talk | contribs)
Jump to navigation Jump to search
Please use "Edit with form" above to edit this page.

Status

Add-on Escape Valve
Stage Draft
Status `
Release target Firefox 10
Health At risk
Status note Currently in the engineering investigation phase

{{#set:Feature name=Add-on Escape Valve

|Feature stage=Draft |Feature status=` |Feature version=Firefox 10 |Feature health=At risk |Feature status note=Currently in the engineering investigation phase }}

Team

Product manager `
Directly Responsible Individual Christian Legnitto
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=`

|Feature feature manager=Christian Legnitto |Feature lead engineer=` |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=` }}

Open issues/risks

  • General engineering spec

Stage 1: Definition

1. Feature overview

Firefox should ship with a restartless installed by default. We could then issue updates to the add-on to ship stopgap fixes silently to users.

2. Users & use cases

  • We ship a new feature (like http:// hiding) and the user response is extremely negative. We issue an update to the add-on that flips a pref back to old behavior
  • We need to distrust a CA. We ship an update to the add-on that makes Firefox distrust it and users are silently updated within 24 hours
  • We have a problem with add-ons that require a rebuild of add-on metadata. We issue an empty update
  • We have an issue that only affects Italian builds. Rather than issue a new Firefox update to everyone, we ship an update to the add-on which only acts when the locale is set to Italian
  • We want to blocklist a widely used plugin. We
  • We know that Netflix/Hulu/etc does bad user sniffing for a particular Firefox version. We issue an update that drops down a infobar telling users what is happening and to contact the site, or we ship the add-on that changes the user agent on the site while they work on a fix
  • We want to speak directly to our users with a one-time marketing message / news flash. We ship an update to the add-on that pops up an infobar with the message and then never shows again

3. Dependencies

  • Leverages existing add-on manager
  • Leverages existing add-on infrastructure
  • AMO would see increased traffic, need to account for that
  • RelEng would have to build it
  • Need processes around creating a stopgap update

4. Requirements

  • Must be hidden / users can't uninstall
  • Needs to be restartless but should support installing a new version that requires a restart
  • Needs to happen at build time and be installed by every Firefox user

Non-goals

  • Ship new features to customers via add-ons
  • Go to Firefox core with functionality broken into add-ons
  • Won't replace the need for software updates

Stage 2: Design

5. Functional specification

  • An add-on is created as part of a normal Firefox build and bundled
  • The add-on cannot be uninstalled or disabled
  • If the add-on is deleted / removed from the user profile it should be copied back
  • The add-on will check AMO for updates
  • The add-on will never uninstall itself

6. User experience design

None required

Stage 3: Planning

7. Implementation plan

  • Investigate what it will take to hide an add-on securely (with no way to disable)
    • In product? Whitelist

8. Reviews

Security review

Things to cover:

  • How to make it so malicious add-ons can't use the same hiding mechanisms
  • How to make it so malicious add-ons can't use the same uninstall prevention

Things already vetted:

  • AMO webservices
  • Add-on manager general functionality

Privacy review

  • Check with privacy team to see if add-ons give additional metrics by default we need to be aware of
  • Before issuing an update get privacy team to sign off

Localization review

  • Should ship with all locales
  • Shouldn't be any localization by default
  • Need to discuss with the l10n team how we could localize if an update needed it

Accessibility

  • Shouldn't impact accessibility

Quality Assurance review

  • QA needs to test the add-on is there
  • QA needs to test the add-on works
  • QA needs to test the add-on can't be uninstalled

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=* General engineering spec |Feature overview=Firefox should ship with a restartless installed by default. We could then issue updates to the add-on to ship stopgap fixes silently to users. |Feature users and use cases=* We ship a new feature (like http:// hiding) and the user response is extremely negative. We issue an update to the add-on that flips a pref back to old behavior

  • We need to distrust a CA. We ship an update to the add-on that makes Firefox distrust it and users are silently updated within 24 hours
  • We have a problem with add-ons that require a rebuild of add-on metadata. We issue an empty update
  • We have an issue that only affects Italian builds. Rather than issue a new Firefox update to everyone, we ship an update to the add-on which only acts when the locale is set to Italian
  • We want to blocklist a widely used plugin. We
  • We know that Netflix/Hulu/etc does bad user sniffing for a particular Firefox version. We issue an update that drops down a infobar telling users what is happening and to contact the site, or we ship the add-on that changes the user agent on the site while they work on a fix
  • We want to speak directly to our users with a one-time marketing message / news flash. We ship an update to the add-on that pops up an infobar with the message and then never shows again

|Feature dependencies=* Leverages existing add-on manager

  • Leverages existing add-on infrastructure
  • AMO would see increased traffic, need to account for that
  • RelEng would have to build it
  • Need processes around creating a stopgap update

|Feature requirements=* Must be hidden / users can't uninstall

  • Needs to be restartless but should support installing a new version that requires a restart
  • Needs to happen at build time and be installed by every Firefox user

|Feature non-goals=* Ship new features to customers via add-ons

  • Go to Firefox core with functionality broken into add-ons
  • Won't replace the need for software updates

|Feature functional spec=* An add-on is created as part of a normal Firefox build and bundled

  • The add-on cannot be uninstalled or disabled
  • If the add-on is deleted / removed from the user profile it should be copied back
  • The add-on will check AMO for updates
  • The add-on will never uninstall itself

|Feature ux design=None required |Feature implementation plan=* Investigate what it will take to hide an add-on securely (with no way to disable)

    • In product? Whitelist

|Feature security review=Things to cover:

  • How to make it so malicious add-ons can't use the same hiding mechanisms
  • How to make it so malicious add-ons can't use the same uninstall prevention

Things already vetted:

  • AMO webservices
  • Add-on manager general functionality

|Feature privacy review=* Check with privacy team to see if add-ons give additional metrics by default we need to be aware of

  • Before issuing an update get privacy team to sign off

|Feature localization review=* Should ship with all locales

  • Shouldn't be any localization by default
  • Need to discuss with the l10n team how we could localize if an update needed it

|Feature accessibility review=* Shouldn't impact accessibility |Feature qa review=* QA needs to test the add-on is there

  • QA needs to test the add-on works
  • QA needs to test the add-on can't be uninstalled

|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=` }}