Small team remote server based simple version control (VCS)

问题

We're a small team and we need to deploy a small, simple and easy to maintain VCS. In past we've been using ftp based sharing where we shared zip of source, we need to improve it. I've been looking for a VCS but not sure how it'll blend into our remote server based environment, most of them are best with intranet.

Environment: We've a Rackspace remove server and team is connected through internet. We work on ASP.Net.

Here're a few options I've come across -

Git / Github
tortoisesvn.net
http://bazaar.canonical.com/en/
www.ftpvcs.com

I've worked with VSS and had some headsup with Tortoise. Is Github the best? Any useful resources to get started would be great. FYI, I can connect to my remote server via Remote desktop (as admin).

BTW, does VS.Net based VSS offer something for remote server based VCS?

Some other ref:

Comparison of top 7 opensource VCS
Using Subversion with FTP

回答1:

I don't have any experience with Git, but we are also using VSS. Here is our scenario for your reference:

We have a server running VSS in our office. All users in the same intranet use VSS client to connect to the server.
Outside the office, our remote team uses VSS remote access add-on - called SourceAnywhere for VSS, to connect to the VSS Server.

This way works well for us.