91–100 of 286 posts
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
... so I decided to destroy it, because I cannot abide things I do not understand.
Seems relevant: https://ruby.social/@getajobmike/115231677684734669 I'm just reposting it though. I haven't followed any of this myself.
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.
Seems relevant: https://ruby.social/@getajobmike/115231677684734669 I'm just reposting it though. I haven't followed any of this myself.
> 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…
Seems relevant: https://ruby.social/@getajobmike/115231677684734669 I'm just reposting it though. I haven't followed any of this myself.
> 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…
Earlier quoted context omitted.
1. You lock everyone out of the org for whichever valid but idiotic reason. 2. The instant you do, you send them all an email explaining the situation. That’s how you do it in those cases. You don’t blindside them and then wait for them to react, restore their access back (which totally negated and nullified the “I wanted to preempt a takeover attempt” argument) and continue to skulk around instead of being open abou…
You're completely right. In a generous interpretation, having so little communication over such a long period is where this went wrong. In any case, having your highly-tenured team dissolve and feeling like things were "hostile," is an indicator that you'll need to do better. Then again, who knows what the goal actually was? Maybe this went perfectly to plan. Given there was nothing approaching an acknowledgement of…
Earlier quoted context omitted.
> 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…
I clarified the toot.
> Why do the maintainers have a problem with this? I thought the stated reason was about RC removing everyone's access with no warning.
I seem to remember some of DHH's controversy due to banning politics at basecamp or something. Is it related to that?
This is not what I had in mind and now I'm embarrassed that I helped make it possible.
Seems relevant: https://ruby.social/@getajobmike/115231677684734669 I'm just reposting it though. I haven't followed any of this myself.
> 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…
Earlier quoted context omitted.
Links: https://rubycentral.org/news/reflections-on-railsconf-2025-f... https://www.linkedin.com/in/shancureton
looking at that CV, I have zero doubt that this will be a subscription service in 5 years time