Roles as described in T721.
User Story
Robert opens Roundcube Files and navigates to a folder containing documents. He clicks on a document and a collaborative editing session is started for him.
Description
Description
Details
Details
- Ticket Type
- Story
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T67 Real-time Collaborative Document Editing | ||
| Restricted Maniphest Task | ||||
| Resolved | machniak | T724 Open collaborative session from Roundcube Files |
Event Timeline
Comment Actions
I've edited the task description to portray the file being clicked is a document, rather than just any file, and the editing session that is opened is a collaborative editing session rather than just an edit session.
The line of thought for the latter part is that most value is in collaborative editing, more so than in just being able to edit a file by oneself as an individual, and the nature of the collaborative editing session does not dictate there are in fact more than one participants in a session -- one could just invite no one else.
If the desire is to indeed allow standalone online editing (no collaboration), then a standalone editing session (including browser close/restart/crash handling) as well as escalating such standalone online editing session in to a full collaborative editing session would require relatively large implementation overhead at relatively little benefit.
Comment Actions
I agree, we should simply use the regular collaborative setup and not worry about providing a single-user mode.