Support Owncloud/Webdav Client for Project Access / Clients / Designers

Description

I often work with graphic designers and as an agency we kinda "force" them to store their word in gitlab repositories to see the history. This kind of people is often not used to the typical uses of git etc. To make it easier for this group of people i kindly like to ask for a webdav access solution for them.

The basic idea is to deliver a virtual filesystem which is build like this:

root folder
  - group folder
     - project folder
        - files and folders of the project

As we have git underneath, the tree should normally also indicate the branches, but this would clutter the tree with duplicate files. Maybe it makes sense to define a branch for webdav usage and make it completely transparent for the user.

Another benefit would be, that designers do not need to configure a repository locally, just the webdav connection once. This means giving access is just a matter of changing rights in gitlab and the corresponding group / project folder will magically appear on the client maschine 😃 .

Currently sparkleshare tries to fill this gap, but imho this is still to complex for that target group.

Heaving that leaves no excuse for not using a VCS system anymore, because there is no need to change anything on the clients except a single installation and configuration of the owncloud client, which does the replication.

Proposal

I kindly ask you to provide a webdav endpoint having the described virtual filesystem to reading/writing files to gitlab.

The implementation is then like a bridge between Webdav and the VCS system.

Links / references