[ruby-core:34126] Re: Moving to Git?

On Thu, Jan 06, 2011 at 02:28:03AM +0900, Jon wrote:
> > Most advantages and disadvantages are already introduced in this
> > list on previous threads.  So summarizing themis needed.
> 
> If this thread restart has any chance of convincing anyone (other
> than enticing Ryan to comment) to move the One True Ruby Repo to
> git, we git partisans should describe _relevant scenarios_ in which
> we've found git makes committers lives _much_ less painful.

I remember most of the previous thread.

I consider myself a well educated DVCS advocate. In Ruby's case, I
cannot think of any real advantage of *dropping* svn support. If at
all, this something Ruby maintainers should decide on internally - and
probably only if svn becomes a pain or starts choking.

Having a svn-only project is a pain for contributors and potential
contributors. With the official public mirror available on GitHub I
believe this and other problems are solved and everyone can be happy:

  - git users can use git or git-svn

  - mercurial user can use hg-git

  - gitub users can fork

  - svn users can spoon, as usual 

  - hardcore svn users can play with Easy Git or just get back to work

If the git and svn repositories are in sync, I don't see a problem.

Perhaps the existence of the official mirror on github is for some
reason not so obvious.

If sometime in the future svn becomes a bottleneck like it would for
Rails or Linux (which are completely different types of projects
compared to Ruby), it might make sense to reconsider throwing out svn
with all the tools (redmine, ...), hooks and making any remaining
scripts around the world referencing the svn repositories fail (rvm
now clones from github - yatta!).

Gcc has an official mirror on repo.or.cz (although the gnu page only
shows svn). If we find any reasons to freeze the svn repo, they
may make sense for the Gcc team also. Until then ...

> Unless someone's able to really articulate git advantage(s) that
> solve _major_ issues for the busy Ruby committer, I don't see the
> value of this thread.

Neither do I. If svn isn't a technical or workflow bottleneck for Ruby
committers, I don't get the point.

Instead of a summary of advantages, could we present a list of options
users have on a page that we could link to? 

I would mention:

  - user can use svn *or* git (both are official)

  - the official github mirror is *really* official

  - using the github mirror instead of svn for building from sources
    is recommended (due to possibility of heavy snow, Godzilla, etc. )

  - how to contribute using git (update the ruby-lang.org link to
    https://github.com/shyouhei/ruby/wiki/noncommitterhowto)

  - possibly add git and svn links on the main ruby-lang.org page


With this info, we could prevent this thread from respawning.

Cheers,

Cezary

-- 
Cezary Baginski