What is the best revision control system for managing approximately?
You have two major Open Source (free) solutions: Git and Subversion.Both of them are great, and I am sure they would work great for you, but i will try to give a pro/con list for each one: [pro] Both are widely used, have plenty of documentation and tools to work with. [pro] Both are open source [pro] Almost all tools that have some integration level with a source control system, start by adding support to one of these two solutionsGit: [pro] Decentralized system. People can commit things even offline and them push changes to the server ... [pro] It is fast. Man, it is fast! It is fucking fast! [con] Git comes with nothing to manage who can do what (as far as I know and searched) natively. But there is an answer to that: Once someone pushes some modification to a central repository, you can choose to merge his changes or not. [con] Git always stores changes of a commit as a whole delta, so there is no way to pick a file in a given revision without having to make the whole code base of a repository branch to the point you want. So suppose you want to make a super-repository with all other repositories ... you can, but ... yeah, that is not very cool on Git. Subversion: [con] Centralized system. There are no commits offline =( [pro] It has a more "straight forward" workflow, since there is no need to keep pushing and pulling changes from other server(s). [pro] You can control who has permission to write or read, and what they can read/write [con] Branching in subversion is easy, as you can read everywhere. But merging back those changes to the trunk can be a pain in the ***! [pro] You can checkout only one file from a given revision, ou a path, or whatever you want, with just a command. [con] Subversion does not keeps track of a checksum of files and changes. This means that if by some weird way, your files get corrupt, you will only know when you see them again or something goes terribly wrong.Hope I gave you some more information on both of them. My advice, if you can do so, it to work with tem both and see what fits more your team.Don't dream that one of them will give you the perfect workflow just after they are installed. The workflow with your team is going to change, no matter what you choose. And the workflow for both tools are relative completely different from each other.I would't change your actual workflow without trying the tool with a small group first.