Page MenuHomePhorge

Joining a collaborative editing session
Closed, ResolvedPublic

Description

Roles as described in T721.

UserStory

Robert opens Roundcube Files and navigates into a shared a folder. The file listing shows that Susy is currently editing a file.
Robert opens the file (doubleclick) to join Susy in the session.
They work on the file together, and when done, Susy selects "Save" and the file is updated in permanent storage and the Roundcube Files listing
reflects the new modified timestamp.

Details

Ticket Type
Story

Event Timeline

petersen raised the priority of this task from to High.
petersen updated the task description. (Show Details)
petersen added a project: Manticore.
petersen changed the visibility from "Public (No Login Required)" to "All Users".
petersen changed Ticket Type from Task to Story.
petersen added subscribers: petersen, vanmeeuwen.

Two angles of attach exist;

  1. List the currently ongoing collaborative editing sessions I'm authorized to participate in,
  2. Navigate a folder hierarchy (including search results and otherwise) annotating files/documents found with the fact a collaborative editing session is ongoing, in which I could participate.

A further question arises, on whether a document to which I have read-only access should be annotated with the fact a collaboration session is ongoing on that particular document.

petersen changed the visibility from "All Users" to "Public (No Login Required)".Sep 8 2015, 7:40 AM

Robert opens the file (doubleclick) to join Susy in the session.

I would advise against it; often, people just want to quickly view a document and that's what they expect from double-clicking it in a web UI. Better would be to provide an action to "edit this document".

Two angles [...]

Both of those approaches are possible because Manticore provides an API to list the documents available to a user, and the response contains "active" status for each document.

A further question arises, on whether a document to which I have read-only access should be annotated with the fact a collaboration session is ongoing on that particular document.

Sounds like a UX problem.

As it works now, if you give a manticore document URL to any other manticore user, even if they do not have write access to a document, they will be able to edit and collaborate on it, but not trigger a save back to the storage. Of course this is a short-term stopgap solution, and we need more serious access control in place first.
So yes, we should keep showing the "active" annotation and allow them to open it in Manticore.

Robert should not be able to just join Susy's editing session without either Susy or the owner of the deployment (and therefore arguably the owner of all files) having pre-approved this level of association of rights outside the session with implicit rights to join and/or manage access on such session.

petersen added a project: Restricted Project.Oct 7 2015, 11:10 AM
petersen added a project: Restricted Project.Oct 27 2015, 4:18 PM
machniak moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
machniak edited projects, added Chwala, Roundcube Kolab Plugins ; removed Manticore.
machniak removed a project: Restricted Project.
machniak moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.