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 08ECD19C04A9 for ; Mon, 30 Nov 2015 00:45: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 66F39B5D853 for ; Mon, 30 Nov 2015 01:16:45 +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 465CE18CC7B6 for ; Mon, 30 Nov 2015 01:16:45 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id B2A7D120491; Mon, 30 Nov 2015 01:16:41 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o10.shared.sendgrid.net (o10.shared.sendgrid.net [173.193.132.135]) by neon.ruby-lang.org (Postfix) with ESMTPS id 5888512045F for ; Mon, 30 Nov 2015 01:16:38 +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=yTL09lzb6bvxMh3MyR3fPtjUHms=; b=Y4AenT2g25GSeLQug4 a3C//Lzys3mF8/1EPg6SspoTHBcKrermO1g1UsrRKbQsWYyBUd3Rk0KdExohzKdV iEKvtZPd8qR8ONM3GsGz2GpLnSiowvSLMjmZzv+3RLkncV6dVgnHq3tGSdJOxWDo E6xSRTy6yjwZ4H3w0WD3RRDlo= Received: by filter0921p1mdw1.sendgrid.net with SMTP id filter0921p1mdw1.8258.565B24E1D 2015-11-29 16:16:33.339798757 +0000 UTC Received: from herokuapp.com (ec2-54-161-103-34.compute-1.amazonaws.com [54.161.103.34]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 2rEeVTz4TFuvoKg4LL5l1A Sun, 29 Nov 2015 16:16:33.656 +0000 (UTC) Date: Sun, 29 Nov 2015 16:16:33 +0000 From: me@jonathanmoss.me 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: 46420 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11741 X-Redmine-Issue-Author: maclover7 X-Redmine-Sender: maclover7 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS4wJrkyNKA+GqOlfvQqK19kFt5hUE2rad2rZn mBkGVvtASqA/hZnPI+rTvs/PHidg8+ePfpSfaVUzlpk11trxxbp6NlNh0AIdLzBRQKAT5jychcd9XG 1OF5JWqObsCtVvE= X-SendGrid-Contentd-ID: {"test_id":"1448813794"} X-ML-Name: ruby-core X-Mail-Count: 71736 Subject: [ruby-core:71736] [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 Jon Moss. Hi Martin, I think my previous response may have come out wrong -- I do think that a service like Gitlab should degrade gracefully, but then again I think the extreme of viewing webpages through a terminal window should not be supported. I downloaded `w3m` onto my computer and used it for a short while to see how it worked with Gitlab, and it seemed fine to me. Eric, would you want to try Gitlab out with `w3m` before the switch? ---------------------------------------- Feature #11741: Migrate Ruby to Git from Subversion https://bugs.ruby-lang.org/issues/11741#change-55141 * 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/