1,273
edits
AMO/FlightDeck/Roadmap: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Dandonkulous (talk | contribs) |
Dandonkulous (talk | contribs) No edit summary |
||
| Line 62: | Line 62: | ||
| We need to analyze and discuss the best way to expose well made user libraries to the community. Will this be a search-based solution, some kind of repository that is managed, or something else that we haven’t considered? | | We need to analyze and discuss the best way to expose well made user libraries to the community. Will this be a search-based solution, some kind of repository that is managed, or something else that we haven’t considered? | ||
| UNKNOWN | | UNKNOWN | ||
|} | |||
</onlyinclude> | |||
== AMO INTEGRATION == | |||
'''Make it easy for developers to use/view AMO features from the Builder''' | |||
<onlyinclude> | |||
{| class="fullwidth-table sortable" | |||
|- style="background:#efefef" | |||
| '''Summary''' | |||
| '''Details''' | |||
| '''Difficulty''' | |||
|- | |||
| Ability to push add-ons to AMO | |||
| FlightDeck should allow developers to push their add-ons to AMO with any associated meta data pre-populated. | |||
| HARD | |||
|- | |||
| Provide AMO status messages | |||
| FlightDeck should sync messages from AMO that let the developer know at what stage in the add-on life-cycle a given add-on is at. | |||
| MEDIUM | |||
|- | |||
| Share AMO sessions via OAuth | |||
| FlightDeck should use AMO’s OAuth service to share sessions, thus eliminating the need for the user to login multiple places with the same credentials. | |||
| HARD | |||
|} | |} | ||
</onlyinclude> | </onlyinclude> | ||