From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-2.6 required=3.0 tests=AWL,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,SPF_PASS,T_RP_MATCHES_RCVD shortcircuit=no autolearn=no autolearn_force=no version=3.4.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id C44501F404 for ; Sun, 25 Feb 2018 16:59:35 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 38D56120926; Mon, 26 Feb 2018 01:59:34 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id 5CAD412091A for ; Mon, 26 Feb 2018 01:59:31 +0900 (JST) Received: by filter0021p3las1.sendgrid.net with SMTP id filter0021p3las1-2567-5A92EB6F-42 2018-02-25 16:59:28.120365922 +0000 UTC Received: from herokuapp.com (ec2-54-234-54-224.compute-1.amazonaws.com [54.234.54.224]) by ismtpd0024p1iad2.sendgrid.net (SG) with ESMTP id y-R0LUHNQ8ORo25u3HfSxA Sun, 25 Feb 2018 16:59:27.950 +0000 (UTC) Date: Sun, 25 Feb 2018 16:59:28 +0000 (UTC) From: shevegen@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 61124 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11741 X-Redmine-Issue-Author: maclover7 X-Redmine-Sender: shevegen X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS7EuAQotK+qlpkk/i0dLqZ+BmOg0C/7lvAofq C6umyV5HR2v15yZauvciaiC2yEA8tWAIbAV3dACbnBmyn8SZKhXrjPDZUCCb3gjfVwPF3t5r6yU9qX pKvf8RVdjgjzoGkru/4bFtFjtmpP2XF3neCGmWvTIZNy/EhqfeeHoIoXYA== X-ML-Name: ruby-core X-Mail-Count: 85807 Subject: [ruby-core:85807] [Ruby trunk Feature#11741] Migrate Ruby to Git from Subversion X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11741 has been updated by shevegen (Robert A. Heiler). > I know this feature request already reject but still posting in > case if guys are still considering to move git. I think it was said that the net benefit may have been too small at that moment in time, but if I remember correctly, it was also said that this can be re-evaluated at a later time. More than two years have been gone by now. :-) (If it is decided to switch to git, I think it should ideally happen before ruby 3.x comes out and probably after mjit has been smoothly integrated.) ---------------------------------------- Feature #11741: Migrate Ruby to Git from Subversion https://bugs.ruby-lang.org/issues/11741#change-70664 * Author: maclover7 (Jon Moss) * Status: Rejected * Priority: Normal * Assignee: * Target version: ---------------------------------------- # 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 Gitlab server s 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/