From: Eric Hodel Date: 2009-09-03T08:29:01+09:00 Subject: [ruby-core:25299] Re: [Feature #2033] Move Core Development to Git On Sep 2, 2009, at 11:19, Run Paint Run Run wrote: > Feature #2033: Move Core Development to Git > http://redmine.ruby-lang.org/issues/show/2033 > > Author: Run Paint Run Run > Status: Open, Priority: Normal > Assigned to: Yukihiro Matsumoto > > Following from [ruby-core:21039], I formally propose that core > development switches to Git. The obvious benefits include: > > * Opens Ruby development to a wider range of contributors. Ruby- and > non-Ruby-based projects alike have shown a dramatic upswing in > contributions after moving to Git. This is scientifically proven? > * Allows tickets to be handled by de facto topic branch maintainers. > A contributor interested in improving documentation, for example, > could review the documentation tickets, apply the relevant patches > to his 'doc' branch, then propose it be merged periodically. The > core team could, and should, still monitor this branch's progress, > and intercede where necessary. Ultimately, development would suffer > less from the current bottleneck effect, allowing contributers to > play a larger role. This sounds like more work than what happens now. How is more work supposed to make ruby development faster? > * Complicated feature proposals would take the form of branches. > This solves the current problem of patches rotting in Redmine > because `rebase` and Git's superior merging capability allow the > patch to be kept in step with the trunk. Further, this allows > parties interested in the feature to collaborate on the branch; only > submitting a pull request when they deem it mature. Can't this be done now with git-svn? > * Experimentation is encouraged because now anybody can branch, and > contribute back that branch, with impunity. Ditto. > * Working with the trunk becomes more pleasurable due to Git's > advanced toolset and significant performance benefits. I've found git less pleasurable and it's "advanced" toolset cumbersome and unfriendly. It's largely been a performance detriment to me.