Issue #11741 has been updated by Jon Moss.


Hi Eric,

I think it's unreasonable to ask a website to degrade and work normally without any GUI or use of Javascript -- these are the core foundations of the web today, and in order to use the web, you must use these technologies. I also think it's uncalled for to ask a website to work through a terminal window -- again, this is not what the modern web was designed for. If you do need Gitlab to work without a GUI or JS, Gitlab has a great API and you can build a small Sinatra app for yourself to consume Gitlab's data.

Most software projects these days (especially ones created in Ruby) do not use mailing lists for contributions. Only the very large ones, like Git and Linux as you have mentioned previously, use mailing lists for contributions. I think using a mailing list as a way to accept contributions would create a very large learning curve for beginners, and would increase the bar for knowledge needed to be able to contribute. I don't agree with you that just because Ruby would be changing to Git, "we ought to adopt the workflows
git developers themselves use." I don't think the toolset that the core Git developers use would be appropriate here, since Ruby is something that's much higher up the technical stack (more abstractions).

I think using something like Gitlab, as compared to Github, is compromise enough for a distributed system, and something that would meet your demands. I am not trying to be rude by saying this, but I don't think the ideology of one person should be holding back a migration like this. I am happy to try and find common ground, but I think some of your requests are a little too much (example would be needing site to be viewable over terminal, with no JS).

Please do let me know if there is anything I can do to help out with this ticket.

----------------------------------------
Feature #11741: Migrate Ruby to Git from Subversion
https://bugs.ruby-lang.org/issues/11741#change-55127

* Author: Jon Moss
* Status: Rejected
* Priority: Normal
* Assignee: 
----------------------------------------
# Git to SVN

Converting Ruby wholesale from Subversion to Git (not necessarily Github!) has been a long time coming, and I think it's finally time to make the switch. Ruby already has an official Git repo up on Github, and the main contributing.rdoc file in that repo is meant for Git, not Subversion. Git is definitely the most popular VCS (version control system) in the Ruby ecosystem, and it's time for the language itself to convert. I propose that Ruby use [Gitlab](https://about.gitlab.com/) to manage its issue tracker, merge/pull request tracker, and the actual Git repository itself. Gitlab is an open source Ruby on Rails that many large corporations have begun to use for Git repository management + related tools. Gitlab also has a CI toolset built right into the core application, so we could also run CI all on the same set of servers. I have contacted and have a sponsor (that's a major Ruby server hosting company) ready to foot the bill for all servers needed to run a cluster of Gitla
 b servers for Ruby.

Below is a preliminary checklist for how to go about the change:

## Actually convert codebase from SVN to Git
  - Either use the **`svn2git`** gem
  - Or clone down the Git repository from https://github.com/ruby/ruby

## Redmine --> Gitlab
  - Contact sponsor [REDACTED] to get GitLab servers spinning, and live (under git.ruby-lang.org, maybe?)
  - Get CI running on Gitlab (start off with Ubuntu Linux)
  - Migrate all issues (open and closed, or just open?) from Redmine to Gitlab via Redmine and Gitlab APIs
  - Begin migrating all pull requests from Github to Gitlab

## Final Transition
  - Post large notice on Redmine website saying that Redmine + Subversion will be deprecated soon
  - After two months (maybe shorter? longer?) close down old Redmine + Subversion servers

I am happy to make adjustments as necessary to the timeline listed above, and to take the lead on this project. Let me know if we want to continue the conversation with the server sponsor and the Ruby core team. <3



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