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 8FC1C19C0031 for ; Thu, 26 Nov 2015 10:37:32 +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 5C9C6B5D883 for ; Thu, 26 Nov 2015 11:08:39 +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 AE65118CC7AF for ; Thu, 26 Nov 2015 11:08:39 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id AAAE8120514; Thu, 26 Nov 2015 11:08:37 +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 2C6B71204C2 for ; Thu, 26 Nov 2015 11:08:33 +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=PYBp93YNaSGJvRc9AtatbliiY9c=; b=RP2cPPdtZ69Ja9+Qu6 zNx+dANVVn6Ufg5zw4xPGgwz6SJowCo2jTIGbhvj3NMEDiD316uOUm1irJisBIXX /kYRW3u+69bKudqhgL+4Vs7/XrtEtEhXf7xB3Nh4Y6fdLDbEbF745nP1AiAdzJTu BMZDROd9OorKEz/j0BpofxtM4= Received: by filter0562p1mdw1.sendgrid.net with SMTP id filter0562p1mdw1.2146.5656697B134 2015-11-26 02:07:55.519463051 +0000 UTC Received: from herokuapp.com (ec2-54-204-208-222.compute-1.amazonaws.com [54.204.208.222]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id yAZc0LoSR2WxVs5pIc3jzg Thu, 26 Nov 2015 01:15:34.429 +0000 (UTC) Date: Thu, 26 Nov 2015 01:15:34 +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: 46370 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS7xg6n4tFmVob3LgZR87X2UJxpJqKFlEExeaE MbtzfrLY2qmTmfUhLqQ2bYB5GrRMQC6Pj03DvQ3telAQcP34LV8fat9ZSTSM7Zetdi6jI2IWZkNApF iI6boq/sp/plCqtwVDgKqGIhVnvXbOCdDMsT X-ML-Name: ruby-core X-Mail-Count: 71692 Subject: [ruby-core:71692] [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: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11741 has been updated by Yui NARUSE. Tony Arcieri wrote: > It seems like this issue addresses at least some of the points raised in #10547, namely the initial steps of a plan to migrate to Git from SVN. > > It also seems like this is an issue that should be periodically discussed, especially if a more concrete plan is forming. Why this is periodically discussed is because anyone doesn't form a concrete plan addressing previous discussion. I know the plan will include some hard work, and believe they can't do that who hesitate to dig previous discussion. > Seeing this issue closed outright without discussion is very frustrating to an outsider. If you really want to join the development of Ruby, you are insider. ---------------------------------------- Feature #11741: Migrate Ruby to Git from Subversion https://bugs.ruby-lang.org/issues/11741#change-55099 * 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/