Good point Garret,
This can get a bit tricky, but each repository can be different. UMNAD
has managed to create plenty of individual units by applying some simple
standard naming conventions.
For example, I could only create repositories that start with enhs-.
Perhaps a simple web-based repo management utility could handle who has
access to what. Each department could have a set of admins, and those
admins could maintain the user access list.
Garrett Kuchta wrote:
> I agree that having a centrally-supported repos is a good idea, but I
> don't necessarily know if SVN is the tool I'd pick. For common-good
> utilities (like authentication modules, drupal mods, etc), managing
> the branching/merging from a large swath of disperete developers could
> get hairy. I think something like GIT (http://git-scm.com/) or
> Mercurial (http://mercurial.selenic.com/) -- something which makes
> branching/merging less painful -- might be better at engendering a
> shared sense of ownership.
> On 05/03/2010 01:48 PM, Debbie Gillespie wrote:
>> Setting up a repository that is accessed via the file system is very
>> easy to do and may be sufficient for many departments. If you want an
>> svn repository that is accessed via https, that is more difficult.
>> For our internal development, we have created a repository on a shared
>> drive. My team can access the repository from the file system
>> (file:///<<path to repository>>) and via ssh (svn+ssh://<<server
>> name>>.<<path to repository>>). Most of our research create svn
>> repository using the same method. For our research groups that need to
>> share a repository with users outside the University, we provide
>> repositories that can be accessed via https.
>> For our internal development, it would be easier for us to continue to
>> host it on our own servers. However, I would be interested in using a
>> centrally hosted repository for our repositories hosted over https.
>> Debbie Gillespie
>> Systems Staff
>> Department of Computer Science& Engineering
>> University of MN
>> Aaron J. Zirbes wrote:
>>> U of MN Developers,
>>> Is there anyone (besides me) out there on the list that feels that a
>>> common-good SVN service would be a good idea? Bad idea? Not sure?
>>> As a web, application and systems developer I feel that I couldn't
>>> do my
>>> job with out a proper revision control system (RCS). It gives me a
>>> giant UNDO button for all of my projects to any commit point in time.
>>> It forces me to comment all my changes. It gives me the confidence I
>>> need to make sweeping changes to a system without the worry of "how
>>> do I
>>> undo this?"
>>> Using SVN has become almost trivial as most development platforms
>>> Dreamweaver included) support SVN out of the box.
>>> We run our own subversion (SVN) server at EnHS for our department's
>>> needs, but I'd be willing to guess that most departments do not.
>>> I know not all departments are large enough to support their own SVN
>>> server, but I feel that any one who isn't using some sort of RCS in
>>> their web development is suffering because of it. It is putting
>>> developers and their work at too much risk. I think that all
>>> at the U should have access to SVN, but for that to happen, U of MN
>>> central would have to set it up as a common-good service.