zlacker

>>bradge+(OP)
This is a great account of "what."

I'm still struggling to understand the "why."

(That's not an implicit criticism of the article, which is extremely appreciated because it's neutral and factual)

I've been away from Ruby for a few years but Shopify always seemed like a huge net positive, sponsoring lots of valuable work on both Ruby and Rails. I never followed Ruby community happenings very closely but I'm not aware of negative feelings towards their community role in the past.

>>JohnBo+PG
It took a fair amount of reading between the lines, but here's what appears to have happened: 1) People and entities with partial control over RubyGems attempted to cancel DHH. 2) In response, elements aligned with DHH kicked the former out of RubyGems. 3) Everyone involved is now attempting to legitimize their motives as "good engineering."

In other words, "When you play the game of thrones, you win or you die."

>>rancor+EJ
I think more accurate is this:

One person who was a major funder of RubyCentral pulled funding because they were upset at RubyCentral platforming DHH. Neither that person, nor RubyCentral, had control over or ownership of the RubyGems software at that time, though RubyCentral operated the rubygems.org service, which uses the RubyGems software.

The corporation that is the other major funder of RubyCentral (Shopify) responded to this (taking advantage of the fact that this left them the sole significant funder of RubyCentral whom RubyCentral could not afford to alienate) to direct RubyCentral to, without any plausible claim of right, seize control of the RubyGems software repos, and kick out anyone who wasn’t a full-time RubyCentral employee from them.

It’s not about DHH except that that indirectly provided the opportunity, it’s about Shopify seeking to consolidate control of core Ruby infrastructure.