130
Mike McQuaid
Mike McQuaid

Having met with both sides on the current RubyCentral/RubyGems situation, here's my take: - RubyCentral have managed this exceptionally poorly in many ways including removing literally the most active member of the RubyGems organisation by mistake who has declined to return - Timeline: RubyCentral had the offer of mediation (from me, others) yesterday, met with me, knew I was meeting with RubyGems maintainers today, engaged with the governance proposals in github.com yesterday, pulled access to maintainers shortly after, announced what they did today.

Proposal for RubyGems Organizational Governance by martinemde · Pull Request #61 · rubygems/rfcs

github.com

- It's been unclear in this whole process where money is coming from, where (and who) it's going to, why and what responsibilities result (or don't) for who from that. This lack of transparency has not helped anyone. - This is a bad day and a bad look for the entire Ruby ecosystem. It makes those of us who actively promote Ruby use for projects look bad. RubyCentral citing "supply chain issues", presumably referencing NPM, in the Ruby ecosystem which handles these dramatically better is unnecessary FUD. - I've been given a lot of private nuance from both sides here but, even just based how the two sides have treated me personally, it's very hard not to put the blame primarily on RubyCentral. I've been a maintainer on Homebrew for 16 years: it's a hard job. If in doubt: I'll side with maintainers. ✌️

Share this Page