[development] FAQ: Why is Drupal still using CVS when X is a much better choice?
jacob at civicactions.com
Fri Aug 1 16:40:33 UTC 2008
As a version control junkie, I would be heavily in favor of this
switch. For development shops, there is an added expense of training /
fixing mistakes when people use CVS. I've been working in IT for 10yrs,
so I know CVS fairly well (although it is foggy), but many of our
developers are 22-25yrs old and have just heard of CVS the way I have
heard of COBOL :).
I can't say I will volunteer however to fix this across the drupal.org
enterprise. What I can do if people are interested is help in securing
funding for some people to do it. I don't know the drupal politics
around this, but I believe this job may simply be too large and complex
to pull off with a volunteer effort.
I don't suppose this is something the Knight foundation would grant
money too, but if not, would it be possible to pass the hat around to
the various Drupal shops to raise money to support a couple people to
take this on full time for a few weeks?
Adrian Simmons wrote:
> Before we once again leave this subject behinds there's just one more
> issue I'd like to see addressed - that of commitment. We have a clear
> desire by most of the community to move off of CVS, clear arguments as
> to why and where to move too and a pretty clear list of what actually
> needs to be done.
> But we're still in a position where those with the power to veto the
> decision to move altogether (Gerhard, Dries? who else?) appear to be
> saying somehting like: "No, I see no advantages, we're not going to do
> Can we have a commitment that *if* everything needing to be done that
> Angie kindly listed on http://drupal.org/node/289117 and links
> therefrom *gets done* we *will* move?
> Without that I just don't see the community putting in the massive
> effort that's required.
More information about the development