ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:71740] Re: [Ruby trunk - Feature #11741] Migrate Ruby to Git from Subversion
Date: Mon, 30 Nov 2015 00:33:19 +0000	[thread overview]
Message-ID: <20151130003319.GA29230@dcvr.yhbt.net> (raw)
In-Reply-To: <redmine.journal-55141.20151129161633.2321d025028e9fe7@ruby-lang.org>

me@jonathanmoss.me wrote:
> Eric, would you want to try Gitlab out with `w3m` before the
> switch?

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.

I've been completely supportive of git since 2005;
never cared for Redmine much, but GitLab seems worse than Redmine.

What happens when GitLab is acquired by another company?  GitLab just
acquired Gitorious this year and shut it down along with all it's
development resources.  I fully expect somebody like GitHub or Atlassian
to buy GitLab one day and do the same thing they did to Gitorious.

Redmine's been through a lot, but hsbt et. al. seem to be doing a
good job of maintaining it so far.

We'd also have to do a lot of work to migrate from Redmine to GitLab;
which doesn't seem to have any tangible benefits[1], only drawbacks I've
noted above.  Even just the SVN-to-git migration could be a lot of work
alone, but adding a needless transition to GitLab is completely
unnecessary.

If people aren't willing to register for a Redmine instance; I doubt
they'd care to register for a GitLab instance, either.  Then we'd also
need to migrate accounts and probably reset everyone's passwords, too
to the annoyance of existing users.


[1] "visually appealing (IMO)" as you noted does not count.
    Especially when the registration page is hostile to non-JS users.

  reply	other threads:[~2015-11-30  0:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11741.20151125234427@ruby-lang.org>
2015-11-25 23:44 ` [ruby-core:71687] [Ruby trunk - Feature #11741] [Open] Migrate Ruby to Git from Subversion me
2015-11-26  0:06 ` [ruby-core:71688] [Ruby trunk - Feature #11741] [Rejected] " naruse
2015-11-26  0:29 ` [ruby-core:71689] [Ruby trunk - Feature #11741] " shibata.hiroshi
2015-11-26  0:35 ` [ruby-core:71690] " bascule
2015-11-26  1:15 ` [ruby-core:71692] " naruse
2015-11-26  2:41 ` [ruby-core:71694] " me
2015-11-26  4:00   ` [ruby-core:71695] " Eric Wong
2015-11-28 16:20 ` [ruby-core:71721] " me
2015-11-28 22:25   ` [ruby-core:71725] " Eric Wong
2015-11-30 11:45     ` [ruby-core:71748] " Rodrigo Rosenfeld Rosas
2015-11-29  5:22   ` [ruby-core:71727] " Martin J. Dürst
2015-11-29 16:16 ` [ruby-core:71736] " me
2015-11-30  0:33   ` Eric Wong [this message]
2015-11-30  1:19 ` [ruby-core:71741] " web2004
2015-12-01 20:58   ` [ruby-core:71784] " Eric Wong
2015-12-27 11:13 ` [ruby-core:72521] " web2004
2016-06-02  9:43 ` [ruby-core:75827] [Ruby trunk Feature#11741] " ferdinandrosario
2016-06-06  5:33   ` [ruby-core:75855] " Martin J. Dürst
2016-07-19  9:21 ` [ruby-core:76442] " naruse
2016-07-19  9:51   ` [ruby-core:76444] " Eric Wong
2016-07-19 19:33     ` [ruby-core:76452] " Eric Wong
2018-02-25 16:59 ` [ruby-core:85807] " shevegen
2019-03-16  9:52 ` [ruby-core:91853] " seo.new

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151130003319.GA29230@dcvr.yhbt.net \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).