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 667A71A40173 for ; Thu, 2 Jun 2016 18:08:28 +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 12625B5D88C for ; Thu, 2 Jun 2016 18:44:00 +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 3EE6E18CC815 for ; Thu, 2 Jun 2016 18:44:02 +0900 (JST) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 484D7120411; Thu, 2 Jun 2016 18:43:59 +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 CE25B120038 for ; Thu, 2 Jun 2016 18:43:55 +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=BdVgQ49vHDC7GVKPQXbv/dB4xps=; b=zMcNZchRvHx5tS1H+3 8OmX5EFvPqQD57lDj1gYCXPLTsqdMCA0o9rP9BdkaJcGh7CKprPK6zCn0o+WMRxV kZqV4DuDCSsVzbv5ib+lgzYl41kkvSRrJFRzjw4WXJKBxnn3GR4+wFvLYKVs/1SE yL/oXHaWw1VZL3qKonITmFSgE= Received: by filter0623p1mdw1.sendgrid.net with SMTP id filter0623p1mdw1.22815.574FFFC73F 2016-06-02 09:43:35.782595814 +0000 UTC Received: from herokuapp.com (ec2-54-163-129-77.compute-1.amazonaws.com [54.163.129.77]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id cuVK4e-eSvmI-pn9b3MaoQ Thu, 02 Jun 2016 09:43:35.651 +0000 (UTC) Date: Thu, 02 Jun 2016 09:43:35 +0000 From: ferdinandrosario@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 50518 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11741 X-Redmine-Issue-Author: maclover7 X-Redmine-Sender: ferdinandrosario@gmail.com 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS4J0jeZihPASRYCWP54vksvGp+RRDcAhkkb0U W0Yy1lZvkW+n7iez5VDRGk7stijwS/DTrPkKlsUQxg1o+jzVHInlgyIcv41uRwrXMbccIjEtKOR92t km9FreXjJypWddOncuJeNHrClfhKUb0LAaUnv3thkI3V8J/gUZrxM+OFZQ== X-ML-Name: ruby-core X-Mail-Count: 75827 Subject: [ruby-core:75827] [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 ferdinand rosario. I know this feature request already reject but still posting in case if guys are still considering to move git. my motivation is not that, python is moving so ruby also has move, instead I love to see ruby in git so that people can contribute to ruby easily. http://www.infoworld.com/article/3077452/application-development/van-rossum-promises-python-36-will-move-to-github.html ---------------------------------------- Feature #11741: Migrate Ruby to Git from Subversion https://bugs.ruby-lang.org/issues/11741#change-59008 * 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 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/