Issue #15605 has been updated by shevegen (Robert A. Heiler).


I think this can be "abstracted" out in the sense of a general mechanism in place when
it comes to gems that are part of the official ruby distribution, and maintainers that
become inactive or at the least less active.

In particular when it comes to pull requests, aka code that already exists but is
not merged in, I agree completely with Charles. (Let's assume here that these 
changes all work fine, without breaking stuff, just to simplify the argument.)

Perhaps a better general solution may be to allow the ruby main team to decide
who is co-owner of gems IF these gems are part of the official ruby distribution.
That way e. g. Charles or other folks (decided by core devs) could at the least
add in the patches. Alternatively things could always be forked anyway and then
merged in.

Since Charles mention it ("find a way to get them push rights"), what would be a
simple way to get others into the position to have push rights? Could that work
on rubygems/gems + rubygems.org alone or does this have to include github-hosted
code? For the latter it may be feasible to have it all under the main ruby 
site on github. (Ideally of course, everything could be managed in-ruby, without
having to depend on any external source, but I also understand that github made
some feature/access simpler.)

IMO this may be something for the next developer meeting - this can happen to 
other gems too, so it seems more general to me.

----------------------------------------
Bug #15605: json library needs more frequent releases
https://bugs.ruby-lang.org/issues/15605#change-76828

* Author: headius (Charles Nutter)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: all
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
There has not been a release of the json gem since April 2017.

Unfortunately there's a long backlog of bugs and pull requests that have been sitting there, including some that prevent users from upgrading JRuby.

I think most of us who have been working on Ruby for any length of time knows that it has been difficult to get json changes released, and it's now starting to really hold back other development.

I propose that we start looking for an alternative maintainer of the library, find a way to get them push rights, and end this bottleneck.

FWIW only flori and I currently have push rights for the gem, but I do not have push rights for the repository.



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