Using Subversion to control public file shares

Where I work, we have folders that a wide range of folks need read/write
access to. Unfortunately, this frequently results in users accidentally
dragging folders around and dropping them in the wrong place. I've
recommended making the file shares read-only, using Subversion to update the
folders and a post-commit hook to export the updated folders and files to
the read-only location.

I implemented this once before at a previous job and never had any issues
with it while I worked there. Before I do it again, I'd like to ask - does
anyone have any *technical* reasons why this wouldn't be a good idea?

I anticipate the pushback from users who will feel that the process is being
made more difficult, but the alternative in my mind is a process where the
shares are restricted to a few users who end up as a bottleneck. With
subversion, the existing list of users can have access, but it's easier to
audit and reverse modifications.
Received on Fri Oct 12 17:20:49 2007