Features/FlightDeck/AMO Integration
Status
AMO Integration | |
Stage | Development |
Status | In progress |
Release target | ` |
Health | OK |
Status note | Currently in the process of moving to AMO OAuth and setting up access to the new AMO APIs. |
{{#set:Feature name=AMO Integration
|Feature stage=Development |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Currently in the process of moving to AMO OAuth and setting up access to the new AMO APIs. }}
Team
Product manager | Daniel Buchner |
Directly Responsible Individual | Piotr Zalewa |
Lead engineer | Piotr Zalewa |
Security lead | ` |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | ` |
UX lead | Daniel Buchner (coord w/ UX) |
Product marketing lead | ` |
Operations lead | ` |
Additional members | Sean McAurthur |
{{#set:Feature product manager=Daniel Buchner
|Feature feature manager=Piotr Zalewa |Feature lead engineer=Piotr Zalewa |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=Daniel Buchner (coord w/ UX) |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Sean McAurthur }}
Open issues/risks
AMO has a new API that is untested and may need modification as we proceed.
Stage 1: Definition
1. Feature overview
Make it possible for users to push add-ons to AMO and sync their states.
2. Users & use cases
The developer finishes their add-on and triggers a push to AMO in the FlightDeck user dashboard. The add-on's review and visible state are then synced to the dashboard.
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=AMO has a new API that is untested and may need modification as we proceed. |Feature overview=Make it possible for users to push add-ons to AMO and sync their states. |Feature users and use cases=The developer finishes their add-on and triggers a push to AMO in the FlightDeck user dashboard. The add-on's review and visible state are then synced to the dashboard. |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 | P1 |
Rank | 999 |
Theme / Goal | ` |
Roadmap | Jetpack |
Secondary roadmap | ` |
Feature list | Jetpack |
Project | ` |
Engineering team | Flightdeck |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=Jetpack |Feature secondary roadmap=` |Feature list=Jetpack |Feature project=` |Feature engineering team=Flightdeck }}
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=` }}