[yawaramin]

Sure, but it's two different things. Maintainers are in charge of their projects, and Ruby Central is in charge of the package index. Each has different priorities, which is fine. If they can't find a way to live with each other, maybe a parting of the ways is required.

[mikemcquaid]

Parting of ways? Sure. In this case they are in charge of the package index but have removed most maintainers from their projects, implicitly taking charge there too. This is a problem.

[yawaramin]

How can they remove maintainers from their own projects? If my project is yawaramin/foobar, how can Ruby Central remove me as the mantainer from there?

[ilikepi]

This thread has probably run its course, and newer postings[1] have more information, but I'll respond anyway if it's helpful...

> How can they remove maintainers from their own projects? If my project is yawaramin/foobar...

The official RubyGems projects in question were under a GitHub organizational account, not a single user's account. A subset of the maintainers had the "owner" flag on the org. One of those folks basically initiated the takeover. See [2] for a more detailed recounting.

[1]: Shopify, pulling strings at Ruby Central, forces Bundler and RubyGems takeover - https://news.ycombinator.com/item?id=45348390 - September 2025 (107+ comments)

[2]: https://joel.drapper.me/p/rubygems-takeover/#the-takeover

[yawaramin]

That's a dumb move though, isn't it? The original maintainers will now just move their projects somewhere else, and the 'official' projects have now effectively been killed. This is a suicidal move for the Ruby ecosystem.

[zem]

do they see themselves as more like debian, where the ruby gem and the open source project it packages are two separate things?