Add-ons/Projects/API: Difference between revisions
Jump to navigation
Jump to search
(Created page with "This is planning or roadmap for the AMO API. == Goals == Produce a good API for AMO. Why? * To support a wide range tools and uses for AMO. * To support new projects to rewr...") |
(→Goals) |
||
| Line 7: | Line 7: | ||
* To support new projects to rewrite AMO. | * To support new projects to rewrite AMO. | ||
* To provide a clear interface between tools and the main server. | * To provide a clear interface between tools and the main server. | ||
* To remove a whole pile of technical debt. | * To remove a whole pile of technical debt and produce a fast, lightweight (and hopefully less complex) base for AMO. | ||
== How == | == How == | ||
Revision as of 21:03, 20 November 2015
This is planning or roadmap for the AMO API.
Goals
Produce a good API for AMO. Why?
- To support a wide range tools and uses for AMO.
- To support new projects to rewrite AMO.
- To provide a clear interface between tools and the main server.
- To remove a whole pile of technical debt and produce a fast, lightweight (and hopefully less complex) base for AMO.
How
Using DRF.
Roadmap
High level road map is something like:
- all the APIs needed for a "view interface" are written: viewing add-ons, installing, searching etc.
- all the APIs needed for a "developer interface" are written: uploading, editing
- all the APIs needed for a "reviewer application" are written
- all the rest
- delete everything that's not an API.
Although this order might be a bit more complicated.