Projects

[ekuiter]

Right now, only one global feature model can be edited.

The following abstraction improves that:

• The server manages projects and users. Users can have permissions (see Authentication & authorization #12) for working on particular projects. Projects and their contents are not related in any way so that different groups of users can collaborate independently (and without disclosing information to each other).
• A project contains editable objects (or variable objects, variability artifacts, ...) There may be multiple objects of the same type (distinguished by name and maybe revision). Objects in the same project may reference/depend on each other, requiring synchronization. Each object can have specific permissions regarding read and write access from users. In the UI, a user can choose an object to edit (maybe multiple objects can be edited, e.g. side-by-side).
• A feature model is an editable object.
• A configuration (see Configuration editor #13) is an editable object referencing a feature model.
• For now, we will neglect revisions and just couple references to the latest referenced object, but a revision system would be possible (merging revisions at a later time is not trivial, though).

[ekuiter]

Implemented in b7e5d99.

editable objects are now simply artifacts. Permissions and configurations are missing, refer to #12 and #13.