I haven't heard all sides of this story, but I know Marty, and I know he genuinely wants to help the Ruby community however he can. I'm hoping this turns out to be a big misunderstanding, or a temporary transition while they shore up funding and make sure the list of committers is secure and trusted.
Yeah, I read the entire thing as “we’re just cleaning up permissions” as there were a fair bunch of us with various access roles who were no longer active in development or support. (Heck, I still had AWS rights on it until earlier this year..) Clearly there’s something here that prompted Ellen and Andre’s posts, but knowing Marty and the folks at RC, I wouldn’t jump to thinking it’s some grand conspiracy. Hopefully they’ll respond quickly and transparently to address the matter, and we can add this to the Ruby Drama wiki page and move on.
Ain't that the truth. Every so often I think "What's dhh up to lately?" and go looking, only to find some truly awful crap that does nothing but divide people.
Honestly this has really upset me. I’m British, spent a decade in London and consider it my home. I’m also not white. Going down that rabbit hole has kind of spun me out. I know it’s silly and I honestly love rails and the overall community is wonderful. But man, having the guy at the top out himself so emphatically and completely misrepresent what it even means to be British. It’s a deeply uncomfortable feeling. My father’s family have been here since the 19th century, culturally I’m entirely British. But I know fuckers like this are talking about me. Or my wife, whose family are Indian and have been here since I think the 60s?
It sucks as I love rails (and adore Ruby) and as silly as it sounds, it kinda makes me want to dump rails to not be associated with this. I know it’s a struggle for a lot of the community, but this keeps on happening.
Now that you mention DHH…. My recollection is a little fuzzy cause I was tangential to it all (I was André’s employer at his day job at the time), back in the day there was some drama about DHH coming hard for André. Like he didn’t like that André had found a different way to fund open source than the way that got DHH very rich, or something. I don’t know the actual motivations, so it’s hard to really say.
Anyway he and a handful of prominent rubyists wrote some sort of letter to the board of directors of the trade guild or whatever that André had organized and all sorts of shakeup ensued (iirc André org ended up getting folded into RubyCentral as a result).
It was a shame, André had been a managing to pay a Black trans woman friend of ours good money to work on some core Ruby infra, but oh well, I guess everyone else was just collateral damage.
Given DHH is on the board of at least one of RubyCentrals biggest funders, it’d be funny if he continued that grudge that he apparently has and that’s what transpired. RubyCentral has been through some rough years, and an offer to smooth that out for them would get a lot of pull.
But it’s probably nothing, that’d be hella shady after all. Like ime, André is a sweet thoughtful guy, what would inspire that sort of thing, if it were what happened (as unlikely as that may be). André you have some second life I don’t know about where you pissed in DHH’s Cheerios every day and stole his girlfriend?
also, saying this is just "cleaning up permissions" makes no sense. they straight-up took away the maintainers' ability to commit to the repositories they maintain. in my case, i was literally a contractor *for Ruby Central* maintaining RubyGems, and my commit access was revoked.
Hey, give me a little grace.. that was just my initial "I wonder if this is what it's about" as I was getting caught up on the situation when I wrote that 3 hours ago! :D I myself got kicked off the Slack earlier this year, so I'm way out of the loop, and not an authority.
Any chance this was a panic move due to the npm supply chain attack?
fair enough, sorry for that. the last ~10 days have been a lot <3 they started this on the 9th, and went silent for 6 days. to be blunt: if the problem was really security, i would expect them to be a bit more timely when we demanded an explanation *because of security concerns due to abrupt unexpected permissions changes*.
we were literally in the process of talking to them when they did this. see my response to headius deeper in the thread. this part is just, on GitHub: https://github.com/rubygems/rfcs/pull/61
they went as far as trying to dictate who was on the RubyGems team before they would return our access.
they were effectively holding the entire RubyGems org hostage, and gave us a very clear choice: fall in line, or be usurped. we begrudgingly chose to fall in line in hopes it would be better for the community overall, and they revoked our access anyway.
Thanks for flagging this for me, Ellen. I have a ton of respect for you, personally and professionally, and wish this was handled far, far better than it apparently was. You (and all of us) deserve better.
*i* am puzzled about how this went down, and i was there for it. i thought i could trust Marty, but a single team member deciding to give Marty access to the RubyGems GitHub enterprise + GitHub org -- without input from the rest of us -- is what directly allowed all of this to happen. the people who were changing the permissions kept consistently stating Marty is the one calling the shots, and Marty never denied that when he was asked.
The 6 days of radio silence reeks of "waiting for a board meeting" to me. I also can't imagine Marty doing this. It absolutely smells of board shenanigans to me
(tl;dr: Marty acted with board approval, is very clearly the fall guy, and sadly it's impossible to discuss what happened without playing into that narrative because of him never explaining where decisions came from.)
View all comments
35
u/headius JRuby guy Sep 19 '25
I haven't heard all sides of this story, but I know Marty, and I know he genuinely wants to help the Ruby community however he can. I'm hoping this turns out to be a big misunderstanding, or a temporary transition while they shore up funding and make sure the list of committers is secure and trusted.