←back to thread

Ruby Central's Attack on RubyGems [pdf]

(pup-e.com)
659 points jolux | 2 comments | 19 Sep 25 08:09 UTC | HN request time: 0.407s | source
Show context
davidw ◴[19 Sep 25 15:37 UTC] No.45302820[source]▶
Seems relevant: https://ruby.social/@getajobmike/115231677684734669

I'm just reposting it though. I haven't followed any of this myself.

replies(2): >>45302882 #>>45302944 #
mijoharas ◴[19 Sep 25 15:47 UTC] No.45302944[source]▶
> The unstated reason for this change was that many of the existing Rubygems maintainers have recently quit (including their only full-time engineer) due to their continued relationship with DHH.

Can someone expand on what this means? Is it a continued relationship between Ruby Central and DHH, or the maintainers and DHH? Why does the other party have a problem with that?

EDIT: It seems the post was clarified since I copy/pasted this, and it's RC and DHH. Why do the maintainers have a problem with this? I though the stated reason was about RC removing everyone's access with no warning.

replies(4): >>45302987 #>>45303007 #>>45303111 #>>45305424 #
mperham ◴[19 Sep 25 15:49 UTC] No.45302987[source]▶
I clarified the toot.
replies(2): >>45303054 #>>45304072 #
1. wild_egg ◴[19 Sep 25 17:14 UTC] No.45304072[source]▶
Didn't RC drop DHH from RailsConf because of his views? Seems weird to think they're collaborate on a coup or whatever is being suggested here.
replies(1): >>45307933 #
2. konnorrogers ◴[19 Sep 25 23:16 UTC] No.45307933[source]▶
They dropped him as keynote speaker a few years ago, and then under new leadership, brought DHH back for the final RailsConf hosted by Ruby Central this year.

The Ruby Central that dropped him is not the same people running Ruby Central today.

https://ruby.social/@rubycentral/114585914969796428