From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 7683319C003C for ; Thu, 26 Nov 2015 08:35:43 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 31720B5D834 for ; Thu, 26 Nov 2015 09:06:50 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 5417918CC7B9 for ; Thu, 26 Nov 2015 09:06:50 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 9FF0F120513; Thu, 26 Nov 2015 09:06:48 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o2.heroku.sendgrid.net (o2.heroku.sendgrid.net [67.228.50.55]) by neon.ruby-lang.org (Postfix) with ESMTPS id 232351204E2 for ; Thu, 26 Nov 2015 09:06:44 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=XEZCJsYyHveIHnfhfvO8vnoIuvE=; b=BPUJtkAzdrFOvtKEJ5 /kbk9YU4PMVclteWUuDOzrxvmb43OriRqrP/z3IplopbDnRA3C5VJzbIuBOsQFEh zw43HCsYJxSAMY5vxmwrBAa5ReLYryuXEb6GNq7rCv+DNgL8EOThaxghpV8A7iMw 9B9uJa2t2O1469HEsghpd25ks= Received: by filter0599p1mdw1.sendgrid.net with SMTP id filter0599p1mdw1.25424.56564D1017 2015-11-26 00:06:40.254284083 +0000 UTC Received: from herokuapp.com (ec2-54-87-102-0.compute-1.amazonaws.com [54.87.102.0]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id m1mSJ1ooROSfn0_IoI3nVQ for ; Thu, 26 Nov 2015 00:06:40.174 +0000 (UTC) Date: Thu, 26 Nov 2015 00:06:40 +0000 From: naruse@airemix.jp To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 46365 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11741 X-Redmine-Issue-Author: maclover7 X-Redmine-Sender: naruse 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS6Pu9r6VkToxq9jy1zMH6UdtpdjNMJv0rNUCM QU4cgAeKateocb8yoe+/Xf1LHe0MAQ2uW6Mh8eyudIJnJMd/lsmVTUNsl+pOHfZLoY3G+aaWxwtezR 1o3UIxug6NMAvsbMt9DRvoGQ2zrUy+tGiyR9 X-ML-Name: ruby-core X-Mail-Count: 71688 Subject: [ruby-core:71688] [Ruby trunk - Feature #11741] [Rejected] 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: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11741 has been updated by Yui NARUSE. Status changed from Open to Rejected Why you don't read previous discussion when you want to discuss about history management. ---------------------------------------- Feature #11741: Migrate Ruby to Git from Subversion https://bugs.ruby-lang.org/issues/11741#change-55092 * 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/