Migrate CVS Ruby Source to Subversion (SVN)?

Has any initiative been taken to help move the ruby CVS source tree to
Subversion? If not, what are the pros and cons of undertaking such a
step?

I’ll admit I’ve left CVS like a bad, old high school girlfriend and
really don’t like talking to her much anymore. Many major open source
projects I’ve followed have already long made the change (apache,
inkscape, rubyforge itself). Still, we should not degenerate into a
personal flame war about our preferences. We should stick to specific
additional benefit, if any, subversion could bring to the core team and
those trying to monitor and suggest clean up of the source–something I
believe I read was now one of matz’ priorities for 2007.

Though the ruby core interpreter source tree seems to have taken a buzz
backseat to the VM work out there, I’d like to volunteer to help get
the core into SVN or at least an SVN mirror. I’m sure there are others
with SVN setup experience that would also volunteer.

[BTW, couldn’t find any topics related to this in my google searches
and though this topic is probably more appropriate to ruby-core, there
may be other “expert newbies” (to borrow and build on Ed’s term) out
their lurking that will find interest. Please don’t read more into this
than is intended.]

On Sat, 30 Dec 2006 23:41:18 -0000, Rob M. [email protected]
wrote:

Has any initiative been taken to help move the ruby CVS source tree to
Subversion? If not, what are the pros and cons of undertaking such a
step?

Check these out:

http://www.ruby-lang.org/en/community/ruby-core/
http://redhanded.hobix.com/cult/rubyIsOffCvs.html

Cheers,