Add-ons/Server: Difference between revisions
< Add-ons
Jump to navigation
Jump to search
(More stuff) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
* increasing the number of add-ons used | * increasing the number of add-ons used | ||
* increasing the number of add-ons developed | * increasing the number of add-ons developed | ||
* improve the add-on usage experience | |||
... and AMO can be instrumental in improving those. | ... and AMO can be instrumental in improving those. | ||
| Line 18: | Line 19: | ||
To assist in supporting the goals, there are some changes in the scope of AMO and what it should support. Those include: | To assist in supporting the goals, there are some changes in the scope of AMO and what it should support. Those include: | ||
* Focusing on add-ons that work on modern versions of Firefox. | |||
* Phasing out add-ons that aren't built on the WebExtensions API, by the end of 2017. | |||
* Assume default add-on compatibility with Firefox. | |||
* Dropping AMO features that don't contribute to the KPIs. | |||
== Short term plans == | == Short term plans == | ||
(Immediate quarter, Q3) | (Immediate quarter, Q3) | ||
* Redoing the mobile pages (more detailed spec to come) | |||
* Get Django to version 1.9 and updating all the packages to the latest versions | |||
* Simplify the add-on lifecycle. [https://docs.google.com/document/d/1OH2iZ7aT9otFJvGTX1UR6pAm58u7ph2Uw8_Zv2Sl8Tk/edit Complete spec]. | |||
** Removing preliminary review. [https://docs.google.com/document/d/1OH2iZ7aT9otFJvGTX1UR6pAm58u7ph2Uw8_Zv2Sl8Tk/edit#heading=h.l5xpme4s155g Section on spec]. | |||
** Allowing easy management of listed and unlisted. [https://docs.google.com/document/d/1OH2iZ7aT9otFJvGTX1UR6pAm58u7ph2Uw8_Zv2Sl8Tk/edit#heading=h.t9v8wvkvot8s Section on spec]. | |||
* Developer and reviewer communication. [https://docs.google.com/document/d/1NeIXRkarfA0RBKuo2wnCzEpgCLwvXm4SlxdSeOiPeMA/edit Spec]. | |||
== Long term plans == | == Long term plans == | ||
Q4 | |||
* Developer hub redesign starts | |||
* Simplify add-on lifecycle (missing work). [https://docs.google.com/document/d/1OH2iZ7aT9otFJvGTX1UR6pAm58u7ph2Uw8_Zv2Sl8Tk/edit Complete spec]. | |||
* Unlisted review tools. | |||
* Admin tools. | |||
* e10s? | |||
( | Future | ||
* Revamp user feedback tools (abuse reports, compatibility reports, ratings, add-on support). | |||
* End user experience redesign. | |||
* Reviewer tools revamp. | |||
Latest revision as of 21:55, 24 June 2016
This page outlines the plans with addons.mozilla.org. There are multiple pages for AMO, but this page should be considered canonical from June 23rd 2016 onwards.
Overview
This page outlines the goals and plans for AMO for the second half of 2016 onwards. AMO has been a major property at Mozilla for over 12 years and is in need of an overhaul and some improvements. The KPIs for add-ons include:
- increasing the number of add-ons used
- increasing the number of add-ons developed
- improve the add-on usage experience
... and AMO can be instrumental in improving those.
Goals
In order to support those KPIs we need to focus on some key goals on AMO. These include:
Scope of AMO
To assist in supporting the goals, there are some changes in the scope of AMO and what it should support. Those include:
- Focusing on add-ons that work on modern versions of Firefox.
- Phasing out add-ons that aren't built on the WebExtensions API, by the end of 2017.
- Assume default add-on compatibility with Firefox.
- Dropping AMO features that don't contribute to the KPIs.
Short term plans
(Immediate quarter, Q3)
- Redoing the mobile pages (more detailed spec to come)
- Get Django to version 1.9 and updating all the packages to the latest versions
- Simplify the add-on lifecycle. Complete spec.
- Removing preliminary review. Section on spec.
- Allowing easy management of listed and unlisted. Section on spec.
- Developer and reviewer communication. Spec.
Long term plans
Q4
- Developer hub redesign starts
- Simplify add-on lifecycle (missing work). Complete spec.
- Unlisted review tools.
- Admin tools.
- e10s?
Future
- Revamp user feedback tools (abuse reports, compatibility reports, ratings, add-on support).
- End user experience redesign.
- Reviewer tools revamp.