In a message dated Thu, 6 May 2010, Brian Mathis writes:
With your firewall issues you will probably be better served with the
distributed VCS tools, like Mercurial, Git, etc... They give each
developer a full copy of the repository, so they won't need to be
accessing over the network all the time. However, they are more
complex.
In terms of understandability, I think a lot of the learning curve for git
and Mercurial and darcs comes from people who made the transition from RCS
to CVS to SVN and have their heads in that space so firmly that they
equate that model with the idea of version control, and have lots of
habits and thought patterns they have to break.
I don't know about the other systems, but I've noticed that people who
start with git without prior knowledge of a version control system seem to
pick it up as quickly as any other system, while people who do know other
systems may struggle. If, as you say, your programmers haven't used any
VCS before, they may not find git all that complex to use. (And setting
it up can be quite simple for the sysadmin for such a small number of
users, assuming you already have SSH access to machines; just set up a
pseudouser with a restricted login shell to own the repositories and give
your programmers' ssh keys access to that pseudouser's account.)
Trey
--
Trey Ethan Harris (/t͡ʃreɪ ˈiːθən ˈhɛrəs/) http://www.lopsa.org/
President, LOPSA -- The League of Professional System Administrators
Opinions expressed above are not necessarily those of LOPSA.
_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
