1,273
edits
AMO/FlightDeck/Roadmap: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Dandonkulous (talk | contribs) No edit summary |
Dandonkulous (talk | contribs) No edit summary |
||
| Line 47: | Line 47: | ||
| Add advanced facets/filters | | 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. | | 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 | | MEDIUM | ||
|- | |- | ||
| Line 140: | Line 140: | ||
| API Stubs | | API Stubs | ||
| Create a UI that allows developers to auto-populate stubs for APIs to the editor that add appropriate code templates and files for the API in question. Comments should optionally be included within the skeleton to describe the various parts of the code and what developers need to input in the unpopulated areas. | | Create a UI that allows developers to auto-populate stubs for APIs to the editor that add appropriate code templates and files for the API in question. Comments should optionally be included within the skeleton to describe the various parts of the code and what developers need to input in the unpopulated areas. | ||
| HARD | |||
|} | |||
</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> | |||
== GITHUB INTEGRATION == | |||
'''Allow users to use Github as their version control system''' | |||
<onlyinclude> | |||
{| class="fullwidth-table sortable" | |||
|- style="background:#efefef" | |||
| '''Summary''' | |||
| '''Details''' | |||
| '''Difficulty''' | |||
|- | |||
| Enable linking of Github accounts | |||
| Developers should be able to link their Github and FlightDeck accounts. This link should provide simple mirroring for add-ons and libraries they choose to host on GitHub. We will not support things like merging and other complex git actions. | |||
| HARD | |||
|- | |||
| Develop a simple push/pull flow from the Builder to Github | |||
| Pulls should sync all local and server stored files with GitHub’s copy of the user’s add-on, if there are unpushed changes, alert the user and require that they either blow out unpushed changes or merge them outside of the Builder. Allow developers to push changes to an associated Github repo if there are no conflicts detected. If conflicts are found, notify the user that syncing is not possible until they resolve the conflicts outside of the Builder. | |||
| MEDIUM | |||
|} | |||
</onlyinclude> | |||
== COLLABORATION AND SHARING == | |||
'''Enable multi-user collaboration and advanced user permissions''' | |||
<onlyinclude> | |||
{| class="fullwidth-table sortable" | |||
|- style="background:#efefef" | |||
| '''Summary''' | |||
| '''Details''' | |||
| '''Difficulty''' | |||
|- | |||
| Ability to add collaborators to add-ons/libraries | |||
| Developers will have the option to grant collaborative permissions for add-ons and libraries to other registered users of FlightDeck. The permissions should account for the following: | |||
- The collaborator can access and edit an add-on or library they are given permission to regardless of its public/private state. | |||
- The add-on or library owner should have control over the collaborator’s ability change which revision is marked as the base version. | |||
- Permissions to edit an add-on or library are package-wide, thus they needn’t be configurable on a per file basis. | |||
- The owner should have the ability to grant permissions that enable collaborators to invite other collaborators. | |||
- The permissions settings for a collaborator should be able to allow or disallow the collaborator from editing the add-on or library’s properties data (Name, Description, etc.) | |||
| HARD | | HARD | ||
|} | |} | ||
</onlyinclude> | </onlyinclude> | ||