Github

Had an interesting meeting with the Github folks today.  As you probably
all know, I have been rather reluctant to switch away from CVS until we
found something that was clearly better.  Until the very latest release
of Subversion, I didn't see it with SVN.  And now with the rise of
Github in the last 3 months and a number of projects making the move I
think we need to take a look at it.

My main concerns with Git through Github is the lack of a granular ACL
system and user definable pre and post commit hooks.  We need both.  The
Github folks will be releasing web service based pre and post commit
hooks soon, and through that we could probably get quite close to our
existing setup.  The work done on the scripts for the Subversion
migration could be changed slightly to provide the backend services for
the Github repository.  But, the Github folks are also willing to add an
ACL mechanism to Github and they would use whatever format we specified
since they said I was the first person to ask them for such a feature.

So, I am definitely not sold on this yet, but outsourcing the source
control work to a very motivated bunch of guys who do nothing but this
stuff appeals to me.  We would be a rather large feather in their cap,
so they are willing to jump through whatever hoops we ask them to jump
through.  For that reason alone we should compile a list of reasons both
for and against a move to Github.

I am fairly comfortable with the state of the Git Windows tools.
TortoiseGit is coming along, and I am told the Git Extensions for the
shell and VisualStudio work well.  The Git cli has been cleaned up as
well, so instead of 200 separate git programs, you now have a very
Mercurial-like cli and writing a git for PHP cvs users page wouldn't be
so hard today.

But, I would really like to hear some dissent on this one.  What have I
missed?

-Rasmus