Issue #21949 has been updated by Eregon (Benoit Daloze). Status changed from Rejected to Open Let me explain my perspective on this: * I contributed significantly to ruby/timeout by [rewriting the implementation to be a lot faster](https://github.com/ruby/timeout/pull/15). * I already acted as a de-facto maintainer by reviewing PRs, triaging and fixing reported issues (some tricky issues which were opened for years). * I think this deserves recognition as being an official maintainer of the `timeout` gem (if not, what are the requirements for it?). * I am happy to have other maintainers for the gem. I think all maintainers should have non-trivial contributions to the gem. Also regarding:
For timeout gem, the remaining issues are too difficult for a single person, IMO.
I solved these issues (except one, where there is a draft PR), so I have shown it is not too difficult for one person to solve these issues. There might more meaning to this than the direct meaning though, which I guess matz would prefer to have multiple maintainers, hence the proposal of having me and @nobu as maintainers. ---------------------------------------- Misc #21949: timeout gem maintainers https://bugs.ruby-lang.org/issues/21949#change-116649 * Author: Eregon (Benoit Daloze) * Status: Open ---------------------------------------- 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 and @nobu (see below) as maintainers 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/