Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby Central's Attack on RubyGems [pdf]

pup-e.com

Post reply on HN
Print view View original

21–30 of 286 posts

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

#21

Post by Antibabelic »

celticninja wrote: post #18
Antibabelic wrote: post #17

Earlier quoted context omitted.

[flagged]

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, you can take the time to type it out yourself.

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

#22

Post by armchairhacker »

krmbzds wrote: 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…

> Even more concerning is the idea that contributor access could become contingent on employment status or ideological alignment. Whether someone is employed by Ruby Central - or holds left-leaning, right-leaning, or apolitical views - should have no bearing on their ability to contribute to open source. Merit, dedication, and community trust must remain the foundation.

Is there any evidence of this? It's not in the PDF.

Also, this comment is clearly AI and more importantly, it affects the quality. Ex: "It's time we demand that the institutions claiming to represent us act accordingly." It seems "the institutions" have been representing them fine until now, why "it's time"? "This was not a misunderstanding. It was a hostile takeover"..."This was a hostile takeover" (or "is", it's still ongoing). "The recent actions taken by Ruby Central - [list]...Ruby Central's actions - [different list]"...the comment tries to explain what Ruby Central has done and what the maintainers demand, but it's vague and disorganized; the linked PDF is better.

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

#23

Post by evertedsphere »

celticninja wrote: post #18
Antibabelic wrote: post #17

Earlier quoted context omitted.

[flagged]

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.

It's not an attack on an idea.

It's pointing out that the person who posted something couldn't be bothered to actually write it themselves. The "content" is the prompt, which is of course never shared because it's probably so trite that it's not going to get anyone's interest unless it's stochastically decompressed into a large amount of text.

Like the sibling commenter, I do not write Ruby and do not care about this conflict apart from a general interest in supply chain stuff. I'm merely tired of the constant encroachment of obvious LLM prose in HN submissions and (albeit less commonly) in comments.

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

#25

Post by byroot »

krmbzds wrote: 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 indeed a malevolent move, but until I've read their side of the story, I'd rather wait and see.

Edit: 35 minutes later, here we go: https://rubycentral.org/news/strengthening-the-stewardship-o...

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

#28

Post by anilgulecha »

Feel bad for the RubyGems community, sending my gratitude and empathy. Ruby was a leap in my career, and i have a soft spot for the language and community

I'll wait for RubyCentral's side on this, but on the face of what's written, these actions do not seem to be transparent or in good faith. Is there something posted from RubyCentral's side?

I wish the Ruby community strength, and a transition over to a community-owned org, one way or another.

(With NPM, WordPress, now this - seems like package repositories are becoming a flashpoint of corporate takeovers..)

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

#29

Post by robin_reala »

politelemon wrote: post #24
robin_reala wrote: post #12

Looks like Homebrew are mediating in some capacity: https://bsky.app/profile/mikemcquaid.com/post/3lz6pkabzwk2o

Why is homebrew involved in this?

Homebrew is one of the most developer-visible Ruby projects around.

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

#30

Post by RobotToaster »

bradgessler wrote: post #19
swilk001 wrote: post #16

Earlier quoted context omitted.

Yes, they recently hired a new Executive Director.

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.
Post reply on HN