By language · Ruby
Abandoned Ruby gems looking for a new maintainer
RubyGems has the most formal "looking for maintainer" metadata of any major registry. The CPAN-style ownership transfer model is the gold standard — and Ruby has been using it since 2014.
Published July 13, 2026 · ~3 min read
The short version
- RubyGems allows multiple owners per gem — the original can stay on while the new maintainer takes over.
gem owner --add <email>is the cleanest co-maintainer handoff of any registry.- Ruby was the original inventor of the "looking for maintainer" workflow.
- Use the GitHub
adopt-metopic +looking-for-maintainerbadge + a pinned issue for the discovery layer.
The RubyGems ownership model
Unlike npm (one owner per package) or crates.io (single crate owner), RubyGems has supported multi-owner gems since the early 2010s. The workflow: the original maintainer runs gem owner --add <new-owner-email>, the new maintainer is now a co-owner, the project can be transferred gradually, and the original maintainer can step back without losing the package name. This is the closest registry-level approximation to the CPAN HANDOFF pseudo-user model. If you maintain a Ruby gem and you're considering stepping back, this is the cleanest path.
If you maintain: the full handoff playbook
Push a final release with a "DEPRECATED" note in the description. Add the GitHub adopt-me topic, the looking-for-maintainer badge, and a pinned "Seeking new maintainer" issue. Drop the project on BreakPoint. The Ruby community is on r/ruby and the Ruby Discord — a "this is a good gem looking for a new maintainer" post will get traction if the gem is genuinely useful. If you find a candidate, run gem owner --add <their-email> and they're now a co-owner — no need to give up your own ownership.