Features/FlightDeck/AMO Integration
From MozillaWiki
< Features
Please use "Edit with form" above to edit this page.
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. |
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 |
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
`
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Jetpack |
| Secondary roadmap | ` |
| Feature list | Jetpack |
| Project | ` |
| Engineering team | Flightdeck |
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
