Issue #10547 has been updated by Shyouhei Urabe.


I have to say sorry about this: matz do not understand the situation.  The situation is that no one in ruby-core is actively willing to do any dirty work to get things move to git.  I think we are all OK when someone else did so.  Right?  The ploblem here is no one wants to seek for the problem here.  It is not just a matter of numbering things.  If you are really willing to push this forward, you need to seek out what are actually preventing the move before fixing them.  No one is active about this right now.

----------------------------------------
misc #10547: How to move the ruby project to git
https://bugs.ruby-lang.org/issues/10547#change-50097

* Author: Sytse Sijbrandij
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
I'm posting this on the bugtracker as suggested by Koichi, feel free to move or close this if I've posted in the wrong project.

During rubyconf 2013 I briefly discussed the migration of ruby from svn to git with the core team. During the Q&A of Rubyconf 2014 Matz again mentioned that the community wants this and there are two problems that need to be solved:
1. Incremental numbering
2. Running scripts

I love ruby a lot and it is the reason I learned programming and became a developer. I now am CEO of GitLab B.V., we make open source software to collaborate on code.

The two problems are things that we can solve in GitLab:
1. Make a project service that tags each commit on master incrementally.
2. Scripts are easy to run on your own GitLab server, see http://doc.gitlab.com/ce/hooks/custom_hooks.html

If the ruby core team is interested we can make 1. and set up a GitLab server, convert the existing scripts and help maintain it for free.

If the core team wants to move to GitHub or Bitbucket we are also willing to help with scripting and conversion.

Best regards,
Sytse Sijbrandij
CEO GitLab B.V.



-- 
https://bugs.ruby-lang.org/