Issue #21949 has been updated by Eregon (Benoit Daloze). hsbt (Hiroshi SHIBATA) wrote in #note-2:
This is already rejected by Matz at https://github.com/ruby/ruby/pull/15424#issuecomment-3640875676
Matz said:
For timeout gem, the remaining issues are too difficult for a single person, IMO.
Hence why this proposal is to have both me and @nobu as maintainers (if @nobu is interested). @matz doesn't that address your concern?
Discussing with multiple people means that it is not good for a single implementation maintainer to make the decision alone.
I don't understand what is meant here, could you clarify? Other gems have multiple maintainers, and there seems to be no problem with it. Are you saying having no maintainers (or effectively "all Ruby committers but none is recognized as maintainer") is better than having multiple maintainers? ---------------------------------------- Misc #21949: timeout gem maintainer https://bugs.ruby-lang.org/issues/21949#change-116643 * Author: Eregon (Benoit Daloze) * Status: Rejected ---------------------------------------- The timeout gem has currently [no official active maintainers](https://github.com/ruby/ruby/blob/master/doc/maintainers.md). I would like to propose myself as maintainer of the [timeout](https://github.com/ruby/timeout) gem. I basically rewrote the implementation in https://github.com/ruby/timeout/pull/15 and acted as a maintainer since then by reviewing PRs and replying to issues. I also recently solved all open issues except https://github.com/ruby/timeout/issues/52 (where I have a draft PR to try to solve it and need more time to validate the fix). Among other [recent active contributors](https://github.com/ruby/timeout/graphs/contributors) I see @nobu, would you like to be maintainer of timeout as well? -- https://bugs.ruby-lang.org/