Services/Sync/Features/Addon Sync
Status
Addon Sync | |
Stage | Definition |
Status | In progress |
Release target | TBD |
Health | OK |
Status note | ` |
{{#set:Feature name=Addon Sync
|Feature stage=Definition |Feature status=In progress |Feature version=TBD |Feature health=OK |Feature status note=` }}
Team
Product manager | Unknown |
Directly Responsible Individual | Unknown |
Lead engineer | Gregory Szorc |
Security lead | Unknown |
Privacy lead | ` |
Localization lead | Unknown |
Accessibility lead | ` |
QA lead | Unknown |
UX lead | Unknown |
Product marketing lead | Unknown |
Operations lead | ` |
Additional members | Unknown |
{{#set:Feature product manager=Unknown
|Feature feature manager=Unknown |Feature lead engineer=Gregory Szorc |Feature security lead=Unknown |Feature privacy lead=` |Feature localization lead=Unknown |Feature accessibility lead=` |Feature qa lead=Unknown |Feature ux lead=Unknown |Feature product marketing lead=Unknown |Feature operations lead=` |Feature additional members=Unknown }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
Add-ons are synchronized between sync clients.
2. Users & use cases
User installs an add-on on one browser. When a sync occurs, the add-on is automagically installed on other sync clients.
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
Add-ons are only synchronized between similar client types (e.g. desktop and mobile). In other words, the add-on set for desktop clients is independent of of that of mobile. The reason for this is add-on compatibility. At the time this was written, most add-ons did not function properly on desktop.
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=` |Feature overview=Add-ons are synchronized between sync clients. |Feature users and use cases=User installs an add-on on one browser. When a sync occurs, the add-on is automagically installed on other sync clients. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=Add-ons are only synchronized between similar client types (e.g. desktop and mobile). In other words, the add-on set for desktop clients is independent of of that of mobile. The reason for this is add-on compatibility. At the time this was written, most add-ons did not function properly on desktop. |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 | ` |
Rank | 999 |
Theme / Goal | ` |
Roadmap | ` |
Secondary roadmap | ` |
Feature list | Services |
Project | ` |
Engineering team | Sync |
{{#set:Feature priority=`
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=Services |Feature project=` |Feature engineering team=Sync }}
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=` }}