Create workflow for projects

[dirkroorda]

A new project starts as follows:

An admin/owner of Pure3D (Susan, Costas) creates a blank project and assigns a user in the role of editor (under the hood we use creator) for this role.

The editor invites sub-editors (under the hood: editors).

editors may modify and delete everything, and may recommend a project for publishing.

sub-editors may modify everything, but cannot delete the project and recommend it for publishing.

editors may invite reviewers (under the hood readers)

Readers may view everything in the project but cannot modify anything.

The admin/owner of Pure3D decides on the publishing recommendation and accepts or rejects it.

Both the admin/owner of Pure3D and the editor can delete an unpublished project.

Once a project is published, nobody can modify the project.

The admin/owner of Pure3D can delete a published project (but not modify it). Deleting a published project should be hard. It is meant for cases where illegal material has been detected.

Probably these rules will be refined in the course of the project.

[dirkroorda]

We have changed our thinking: the roles of creator/editor/reviewer is relative to editions, and there is a new role, manager aka organiser relative to projects.

Editions are published. Projects are set to visible.

[dirkroorda]

Project/edition creation and updating is more or less done.

What remains are the workflow steps of publishing.

Idea: when an organiser publishes an edition, it becomes frozen, but the organiser can unfreeze it within a week. After that week, the edition becomes permanently frozen.

[dirkroorda]

We close the issue now. Publishing is dealt with in #9 .