We have finished the application design and data modeling phases of a system to be coded during the next 12 months or so. The programming team will consists of a friend and I, working at separate locations.
Our initial desire would be to go with Team Foundation Server for both revision control and work item tracking. But we hit an impossible obstacle: The requirements are TFS 2010 and SQL Server 2008 R2. The idea of purchasing a Virtual Private Server where these could be installed and act as our Team Foundation Server would mean a very high initial cost. I'd have to upload to the server well over 2Gb just for installation files (which would actually require me to edit the SQL server installation disk to remove the x86 and itanium setups, otherwise make that 6Gb). With the typical 1Gb monthly bandwidth minimum, you can see the problem with that.
We may find another way to deal with WIT. Or just ignore it altogether for now and adopt stone age project management strategy. But revision control is essential.
So I'm considering adopting for the first time a distributed revision control system. I would require something easy to work, with a small entry cost. Frankly I'm in no mood to spend an inordinate amount of time learning a revision control when what I should be doing is coding. Any suggestion in this direction would be great. It's my first time with DRC systems.
...
On a silly note... I actually considered using dropbox with subversion. It actually works great. But how unprofessional (and insecure) would that be. In any case, there's a tip for anyone not doing anything too big or meaningful and not wanting to go with distributed revision control.
