Live data from Hacker News

Ruby Central's Attack on RubyGems [pdf]

pup-e.com

31–40 of 286 posts

Re: Ruby Central's Attack on RubyGems [pdf]

#31
post #25
post #13

The recent actions taken by Ruby Central - removing long-time RubyGems and Bundler maintainers without warning, seizing administrative access, and consolidating control under a small, centralized group - represent a serious breach of trust within the Ruby ecosystem. This was not a misunderstanding. It was a hostile takeover of key infrastructure, undermining both the long-standing maintainers and the broader communit…

> What we've witnessed over the past week Who is "we"? And what did they witness? All we got right now is one side of the story. It is indeed surprising such change wouldn't be immediately followed by a public announcement, but they've been founding and managing RubyGems for a very long time now, so it's not even clear to me how this can be a "takeover". I'll happily join with my pitchfork if it turns out this is ind…

All we got right now is one side of the story

That's because Ruby Central chooses not to communicate. I'm not going to reserve judgment against intentionally mute hostile actors.

Re: Ruby Central's Attack on RubyGems [pdf]

#32
post #5

Copy-pasted below for posterity in case it goes down because I think this is a huge deal: ## Ruby Central’s Attack on RubyGems Hi! I’m Ellen, but you probably know me as duckinator or puppy. I really wish I didn’t have to write this, but I feel the Ruby community needs to know it. I have been part of the Ruby community since I was 13, and one of the RubyGems maintainers for the last decade. This community has helped…

https://web.archive.org/web/20250919130055/https://pup-e.com...

Re: Ruby Central's Attack on RubyGems [pdf]

#34

Earlier quoted context omitted.

Links: https://rubycentral.org/news/reflections-on-railsconf-2025-f... https://www.linkedin.com/in/shancureton

Someone with absolutely no technical background, a recipe for disaster.

Opposed to hiring someone with a technical background but no experience running a non-profit?

Re: Ruby Central's Attack on RubyGems [pdf]

#35

Earlier quoted context omitted.

what are these hallmarks? is this becoming the latest way to attack an idea? instead of engaging with the actual content you just claim it is AI and therefore it can be ignored? seems disingenuous to say the least.

Overuse of rule of three, cliches like "This was not X. It was Y." and similar, obligatory bulleted list, overall overly grandiose. None of these are a smoking gun, but the smell is definitely here. AI detection tools also confirm my suspicions. I don't have a horse in the race in regards to the content, since I'm not a Ruby developer, I would just prefer to not see AI-written comments on HN. If this is so important,…

[deleted]

Re: Ruby Central's Attack on RubyGems [pdf]

#36
post #31
post #25

Earlier quoted context omitted.

> What we've witnessed over the past week Who is "we"? And what did they witness? All we got right now is one side of the story. It is indeed surprising such change wouldn't be immediately followed by a public announcement, but they've been founding and managing RubyGems for a very long time now, so it's not even clear to me how this can be a "takeover". I'll happily join with my pitchfork if it turns out this is ind…

All we got right now is one side of the story That's because Ruby Central chooses not to communicate. I'm not going to reserve judgment against intentionally mute hostile actors.

Organizations are necessarily slower to communicate than individuals, give them a couple days. People need to chill out before jumping to conclusions like that.

Re: Ruby Central's Attack on RubyGems [pdf]

#37
post #34

Earlier quoted context omitted.

Someone with absolutely no technical background, a recipe for disaster.

Opposed to hiring someone with a technical background but no experience running a non-profit?

Non sequitur. False dichotomy.

Re: Ruby Central's Attack on RubyGems [pdf]

#38
post #8

Could someone with more insight as to the decision-making at Ruby Central weigh in on what's going on here? Between this and drama with the conferences over the years I'm just confused. They've been busy launching podcasts and doing fundraising, email campaigns and all that. Has there been a change in leadership?

I'm still not clear about why they dropped RailsConf. I assume the biggest sponsors threw their weight behind Rails World?

Re: Ruby Central's Attack on RubyGems [pdf]

#39
post #36
post #31

Earlier quoted context omitted.

All we got right now is one side of the story That's because Ruby Central chooses not to communicate. I'm not going to reserve judgment against intentionally mute hostile actors.

Organizations are necessarily slower to communicate than individuals, give them a couple days. People need to chill out before jumping to conclusions like that.

Based on the OP, the initial changes were made 10 days ago - more than enough time to communicate something publicly.

Re: Ruby Central's Attack on RubyGems [pdf]

#40
post #25
post #13

The recent actions taken by Ruby Central - removing long-time RubyGems and Bundler maintainers without warning, seizing administrative access, and consolidating control under a small, centralized group - represent a serious breach of trust within the Ruby ecosystem. This was not a misunderstanding. It was a hostile takeover of key infrastructure, undermining both the long-standing maintainers and the broader communit…

> What we've witnessed over the past week Who is "we"? And what did they witness? All we got right now is one side of the story. It is indeed surprising such change wouldn't be immediately followed by a public announcement, but they've been founding and managing RubyGems for a very long time now, so it's not even clear to me how this can be a "takeover". I'll happily join with my pitchfork if it turns out this is ind…

> All we got right now is one side of the story

Well, we have all of Ruby Centrals actions including their action to not be more public during these actions. Their actions are their story. If their actions don't communicate their intent, that is on them to handle that in a professional way to not be in this situation.

Post reply on HN