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 (Adobe > 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 developers > 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. > > -- > Aaron >