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 4260019C0031 for ; Thu, 26 Nov 2015 09:04:21 +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 016A8B5D832 for ; Thu, 26 Nov 2015 09:35:28 +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 41B6218CC7CC for ; Thu, 26 Nov 2015 09:35:28 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id C65C012050F; Thu, 26 Nov 2015 09:35:26 +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 E7D441204E2 for ; Thu, 26 Nov 2015 09:35:22 +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=e04y5ho0YTMU/F3pW9acSOk7ccQ=; b=fXccakiBGpanjL5xYc vv11LWCYfrw/aJQRnrmXkB5xtkGTAmC69QPDulJfcDfDC4qE7dd0d+aEN+q2+HeK QFmmCWCDZ1y/CrZQTCq6WyNvSyJakBLqgfmGBdgrjhnm7dkMsVB12tO5EApfZyHz Oc1Q/BqpzfREhTzYyPtfFeIQE= Received: by filter0509p1mdw1.sendgrid.net with SMTP id filter0509p1mdw1.20724.565653C64C 2015-11-26 00:35:18.570246007 +0000 UTC Received: from herokuapp.com (ec2-54-87-78-110.compute-1.amazonaws.com [54.87.78.110]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id fBS1XpHIT-uiEvzx84nrAA Thu, 26 Nov 2015 00:35:18.542 +0000 (UTC) Date: Thu, 26 Nov 2015 00:35:18 +0000 From: bascule@gmail.com 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: 46367 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11741 X-Redmine-Issue-Author: maclover7 X-Redmine-Sender: bascule 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS7Tb92cVQTxk8hJh1YlmO/vFgwmzeefcV6w7B gx/02X9EQTOPr8eWLKy9H93nLkPOwn9cLuk1MewUngocPH2BTYjlU1ucUG1+gjQmBYbZGnEgGNTZ+0 GRlOC5NzpeFRbLwAqCJF61iWrSRdvfPD9xQk X-ML-Name: ruby-core X-Mail-Count: 71690 Subject: [ruby-core:71690] [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 Tony Arcieri. It seems like this issue addresses at least some of the points raised in #10547, namely the initial steps of a plan to migrate from Git to SVN. It also seems like this is an issue that should be periodically discussed, especially if a more concrete plan is forming. Seeing this issue closed outright without discussion is very frustrating to an outsider. ---------------------------------------- Feature #11741: Migrate Ruby to Git from Subversion https://bugs.ruby-lang.org/issues/11741#change-55096 * 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/