[#119637] Behavior of raising from rescue blocks when multiple rescue blocks exist — Rodrigo Rosenfeld Rosas via ruby-core <ruby-core@...>
Hello, I couldn't find any documentation about the subject, so I thought
3 messages
2024/10/29
[ruby-core:119473] [Ruby master Misc#20746] Request to migrate the json gem from flori/json repository to ruby/json
From:
"hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@...>
Date:
2024-10-07 03:38:17 UTC
List:
ruby-core #119473
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/