Issue #18975 has been updated by k0kubun (Takashi Kokubun). Status changed from Feedback to Closed We discussed this again in the DevMeeting-2022-12-15. We agreed to make the following changes after the Ruby 3.2 release. Now that Ruby 3.2 is released, I'm publishing this update and making permission changes on the IRB repository. ### Ruby 3.2 This year, Reline and IRB have been maintained as follows: * reline * Maintenance (git push only): ima1zumi, hasumikin * Release: hsbt * irb * No maintainers. Any committers merge bug fixes. * For features like adding commands, Stan and I can review each other’s PR and merge it. * Release: k0kubun or hsbt ### Ruby 3.3 We agreed to make the following changes from the Ruby 3.3 development. * reline * Maintenance **+ Release**: ima1zumi, hasumikin * irb * **Make Stan, ima1zumi, and hasumikin the new IRB maintainers.** * New features can be merged if those three maintainers agree on it. * The maintainers will get GitHub write access on ruby/irb. * Release: k0kubun or hsbt will continue to do it at first, but revisit this later. Looking forward to making IRB and Reline better with you all :) ---------------------------------------- Misc #18975: Propose Stan Lo (@st0012) as an IRB maintainer https://bugs.ruby-lang.org/issues/18975#change-100805 * Author: k0kubun (Takashi Kokubun) * Status: Closed * Priority: Normal ---------------------------------------- ## Background Looking at @aycabta 's GitHub activity, he's been inactive on the Internet for 6~7 months, which means that IRB hasn't had the maintainer during that period of time. While I managed to sneak in some IRB changes when he was active, I personally have some more IRB changes that I want to make, but I'm not sure if we're gonna make it to Ruby 3.2 since we can't predict when he'll be back and there's nobody taking the ownership of the IRB design now. However, I don't think the 2nd most active contributor (@nobu) is particularly interested in IRB, and the 3rd most active contributor (myself) currently doesn't have capacity to maintain anything new. So having a temporary maintainer from existing committers could also be hard. ## Proposal I propose to make Stan Lo (@st0012) a new committer and a co-maintainer of IRB. He's best known for being almost as active as @ko1 in [recent debug.gem development](https://github.com/ruby/debug/commits?author=st0012) and I think he deserves maintainership in the Ruby's debug tooling area in general. While he has fewer contributions to IRB, some modules of IRB (which I authored, so I should have a say) are used by debug.gem, so I believe IRB being maintained by him will also be useful for the success of debug.gem and Ruby 3 tooling. -- https://bugs.ruby-lang.org/