Joel Drapper, a Ruby developer, writes about the Ruby Central and RubyGems takeover, and about his own Ruby libraries and tools.
Commenters repeatedly link his RubyGems takeover post as the account that Shopify forced the hostile takeover through Ruby Central, against long-term maintainers.
I can see how you're coming away from this article with that perception, but, this needs to be read in the context of everything said prior: its intent isn't to provide you a full narrative of the situation, just additional context.
This article is the missing piece explaining why:
1. Shopify, allegedly, "specifically demanded that at least one of the RubyGems maintainers, André Arko, be excluded from returning to the project."[0]
2. Rafael França, a member of Rails Core, publicly listed concerns[1] about "competitor tooling"/"admin trust" r.e. rv.
Both are components of Joel Drapper's post that gave me pause on my first read, as these statements aren't something said without basis. That basis being correct or not is another matter, but I wouldn't expect either Shopify or a member of Rails Core to have such concerns simply because they don't like someone.
Personally, I don't come away from this article with the sense the author dislikes André, just that there's perhaps more rationale coming from a camp that's largely not said much so far.
Looking into the crystal ball of future predictions, the battle lines we're going to see in the Ruby community will be based around the acceptance or rejection of some of the allegations here about Ruby Together's spending.
I recall Ruby Together advocating for personal sponsorships in addition to corporate. It's one thing to be treating Apple adapters as disposable HB pencils & buying dinners on the company card if companies are…
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
Well, there's more information out and it seems pretty.. damning. I wasn't convinced by "power grab", but "economic pressure from our sole remaining major sponsor" is _way_ more believable, and the chain is events is getting fairly clear. Check out Joel's explanation for a coherent delve into the events: https://joel.drapper.me/p/rubygems-takeover/
Now I just have to hope the fallout from this includes a less centralized replacement for the tools I'm used to - I haven't found anything solid yet, but I imagine andre will be examining this problem space with rv now.
One possible trigger for this fiasco is that André Arko and the Spinel Coop are working on rv, a Rust-based replacement four the Rubygems client. If it is as successful as uv has been for Python, it could disintermediate rubygems.
Joel Draper says as much (see the penultimate section of https://joel.drapper.me/p/rubygems-takeover/) although that would be more of a motivation for RubyCentral than for Shopify.
For me, most people that are involved (e.g. simi, a, now former, maintainer[0]) seem to point to this post by Joel drapper as a canonical and accurate accounting of events, and I have no reason to doubt them[1]. Most of the article says it's due to pressure from Shopify.
[0] https://gist.github.com/simi/349d881d16d3d86947945615a47c60ca
[1] https://joel.drapper.me/p/rubygems-takeover/
https://joel.drapper.me/p/rubygems-takeover/
Read the above, but tl;dr is that Shopify executed a hostile takeover of Ruby Central for its own benefit, at the expense of long-term maintainers and the general community. I'm not sure if there's been any real change since then, but there are many reasons not to trust anything that the board says at this point.