AMO/FlightDeck/Roadmap: Difference between revisions
< AMO | FlightDeck
Jump to navigation
Jump to search
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> | ||
Revision as of 23:02, 27 June 2011
APP HARDENING
Refactor client-side code and the related server-side pieces that support it
| Summary | Details | Difficulty |
| Retrofit the site’s JS code with client-side MVC model | The JavaScript needs a major refactoring and integration of a cleaner JS MVC system. | HARD |
| Revision queue for editor actions | Create a back-end mechanism that organizes and executes revisions in the proper order, regardless of how or when various async, revision-creating events finish processing. | HARD |
| Refactor and clean-up CSS | The CSS across the site is redundant and sub-optimal. We will refactor and slim down all the style sheets that need it. | MEDIUM |
| Increase page load performance | Minify and gzip all assets, integrate a legit dependency system in FlightDeck. | EASY |
| Package build speed optimization | Look into both software and hardware options for decreasing build times and increasing stability of the service. | UNKNOWN |
| Update ACE editor to latest stable version | Update the ACE editor and ensure that it recognizes and correctly handles debugging suggestions for the advanced ES5 keywords and methods found in Firefox. | MEDIUM |
ADVANCED SEARCH
Provide advanced search facets/filters and better fuzzy search
| Summary | Details | Difficulty |
| Add advanced facets/filters | FlightDeck search should allow for more advanced facets and filters that allow developers a more convenient way to find the result set they are looking for.
filter: author/owner filter: dependencies facet: number of forks facet: most active (recency of last update in ratio to # of total commits divided by age) facet: size of the add-on/library facet: number of dependencies |
MEDIUM |
| Enhance fuzzy search | The full-text search should be augmented to allow for fuzzy search in the same vein as other full-text search engines like Solr. | UNKNOWN |
| Develop a system for elevating user libraries | 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 |
AMO INTEGRATION
Make it easy for developers to use/view AMO features from the Builder
| 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 |