Issue #11741 has been updated by Sytse Sijbrandij.


Eric Wong wrote:
> web2004 / sytse.com wrote:
>  > Eric Wong <normalperson / yhbt.net> wrote:
>  > >  The main site's Terms of Service (or any ToS) is still a problem
>  > >  for me.  Currently there is no ToS at all on our Redmine instance
>  > >  and registration is completely non-intuitive on GitLab w/o JS.
>  
>  > 1. Is this about the terms of service for GitLab.com or something
>  > else? Since I think a self hosted GitLab instance is proposed I think
>  > there are no ToS.
>  
>  OK for the proposed instance.  But if we find a problem with the hosted
>  instance and want to report the problem to GitLab itself, the reporter
>  would still have to deal with the ToS of GitLab.com

If reporting bugs about GitLab by the ruby tema is a problem we would be happy to provide this via email like we do for our customers.

>  > 2. If better non-javascript functionality is needed for the conversion
>  > to happen we would be happy to add that.
>  
>  For one, the registration page I noted earlier only shows a bunch
>  of unlabeled input boxes on w3m (which has no JS or CSS support).

Thanks, I've created https://gitlab.com/gitlab-org/gitlab-ce/issues/4316 for this. We would be happy to fix this.

>  Does GitLab have mailing list integration?  Fwiw, I would not have
>  bothered contributing to Ruby if we did not have ruby-core mailing list
>  integration with Redmine (but I'm only an occasional contributor to
>  Ruby).

We're thinking about this in https://gitlab.com/gitlab-org/gitlab-ce/issues/4272

>  > 3. If GitLab Inc. is acquired by another company (which is unlikely)
>  > GitLab the project will still continue. It is in use by more than
>  > 100,000 organizations and has over 800 contributors and is MIT
>  > licensed.
>  
>  It's likely the Gitorious guys were thinking the same a few years ago :)

Of course I can't predict the future but we have over 40 team members, are well capitalized and are close to cash flow break even this month. The situation is not similar to that of Gitorious during their lifetime.


----------------------------------------
Feature #11741: Migrate Ruby to Git from Subversion
https://bugs.ruby-lang.org/issues/11741#change-55785

* 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/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>