1,273
edits
AMO/FlightDeck/Roadmap: Difference between revisions
→COLLABORATION AND SHARING
Dandonkulous (talk | contribs) |
Dandonkulous (talk | contribs) |
||
| Line 177: | Line 177: | ||
| Ability to add collaborators to add-ons/libraries | | 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: | | 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> | ||