From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
Subject: [ruby-core:119473] [Ruby master Misc#20746] Request to migrate the json gem from flori/json repository to ruby/json
Date: Mon, 07 Oct 2024 03:38:17 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-110090.20241007033817.7941@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20746.20240916080221.7941@ruby-lang.org>
Issue #20746 has been updated by hsbt (Hiroshi SHIBATA).
Status changed from Open to Closed
Assignee set to hsbt (Hiroshi SHIBATA)
flori transferred json repo under the Ruby organization today. We have https://github.com/ruby/json now.
----------------------------------------
Misc #20746: Request to migrate the json gem from flori/json repository to ruby/json
https://bugs.ruby-lang.org/issues/20746#change-110090
* Author: byroot (Jean Boussier)
* Status: Closed
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
### Context
The `json` gem, which is part of Ruby's default gems, is the only default gem (aside from `rubygems` itself) for which the source repository isn't under the `ruby/` organization.
@naruse and @hsbt, the two maintainers have merge permission into the repository, and gem ownership on, but no administrative right.
The sole repository administrator is @flori, but he has been inactive for years.
### Problem
- This prevent the maintainers to change the repository configuration to change CI and other integrations.
- This prevent the maintainers from giving commit bit to others, e.g. JRuby/TruffleRuby maintainers.
@hsbt has been trying to contact @flori for over two years now (first email in June 2022) and never got any answer.
Later on we tried to contact him via GitHub where he seems active: https://github.com/flori/json/issues/591, but without success. I even asked him to please respond after he merged one of my contribution to one of his projects, but he ignored that too: https://github.com/flori/term-ansicolor/pull/38#issuecomment-2263838711
### Proposal
To resolve this situation I propose the following:
- Create a copy of the repository at `ruby/json`.
- Update the `json.gemspec` to declare `ruby/json` as the gem official repository.
- Resume development there.
NB: This is not taking anything away from @flori, if he wishes to remain administrator of the repository, we can perfectly add him as administrator of `ruby/json`.
cc @Eregon
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next prev parent reply other threads:[~2024-10-07 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 8:02 [ruby-core:119212] " byroot (Jean Boussier) via ruby-core
2024-09-16 11:38 ` [ruby-core:119216] " Eregon (Benoit Daloze) via ruby-core
2024-10-07 3:38 ` hsbt (Hiroshi SHIBATA) via ruby-core [this message]
2024-10-08 0:27 ` [ruby-core:119477] " hsbt (Hiroshi SHIBATA) via ruby-core
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-110090.20241007033817.7941@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@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 NNTP newsgroup(s).