Version control system for a small laboratory?

We use subversion and love it, for its simplicity, easy of use, integration into the shell environment and the ability to not just version, code, but also specification documents pdf's and other resources we have.

We use subversion and love it, for its simplicity, easy of use, integration into the shell environment and the ability to not just version, code, but also specification documents pdf's and other resources we have. As for structuring it, try and use your logical structure, as close as possible. Keep it simple :).

I see no reason why you should look further from Subversion. Although, for extra little maintenance you could check GitHub (since it is hosted solution, so no worrying about backup, servers etc) but there are hosted Subversion repos as well. Especially if you're already familiar with it, so you can bring others up to speed and get extra credit :).

Once completely setup subversion should require very little maintenance, it's model is simple to apprehend, it is integrated in the shell, it supports ACLs which work just fine and it's setup is well documented. You can setup subversion in a webserver, integrate it with a windows domain for auth if needed (otherwise you have to add/remove users, change passwords on the svn server) You could also go the distributed vcs way, with hosted solutions no server setup, but to get that across your user's mind is gonna be way more difficult than svn. Not to mention getting it across your own head first.

Unless you have complex, fast-paced, parallel development models, I wouldn't recommend dvcs, I would stick to SVN.

I agree that subversion is a very good choice. But you can also consider mercurial: it's easier and it also has a tortoise integrated interface.

– rlbond Jan 26 '10 at 17:17 @ribond It's not my direct experience. I was told it's easy to setup and use. One big difference is that mercurial is a distributed version control system, like git.

I will try mercurial for my next project. – sergiom Jan 27 '10 at 8:40 @ribond this old topic looks interesting: stackoverflow. Com/questions/224396/… – sergiom Jan 27 '10 at 8:47.

I would recommend assembla.com. They offer paid subscriptions but for academic projects you can apply for a free pro account. I have used it for my academic projects and was 100% satisfied by the ease of maintenance, up-time and simplicity.

The far easiest way is to use Subversion. But to get it to work the most easiest way (under Windows) you should definitely use TortoiseSVN. After installation it works right within the explorer is just one right click away from usage.

Maybe one of your guys should take a deeper look into the whole documentation to give help if needed. All other guys should take a look into the Daily Usage Guide for a first start. Also you should take care about how you structure your repository!

Subversion has too many limitations related to the "always online + central server" model. I would strongly recommend using a distributed version control system. From the three main ones Git, Mercurial, Bazaar; in my experience Bazaar is by far the easiest one to use and setup.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.