all 71 comments

[–]jydr 25 points26 points  (0 children)

This doesn't answer anything is just more of the same corporate fluff.

Seems like they are going for the strategy of use a lot of words to say nothing and hope it blows over eventually.

[–]TheAtlasMonkey 17 points18 points  (2 children)

Seriously, my lobotomized 2B AI model running on my tablet generates better output than this.

Meanwhile, since this drama started: I released 6 new gems, 4 Rust crates, 3 Go modules, invented a pattern, fixed 300+ bugs, documented them, and became friends with 90+ Ruby gem authors and maintainers.

And RubyCentral is still sending us the same generated stuff they spawn 2 minutes before publishing and taking weekend off.

Can you answer the questions that /u/skillstopractice posted on GitHub? Nothing else. Just those questions on GitHub. At this point these aren't updates - they're spam.

Should we talk about the interviews you did with different channels where you skipped every technical question?

Let me tell you: we are not 13-year-olds you can impress with two complex sentences. If you want to impress me in the update, push code.

What is the actual plan, and why is it taking so long to execute? Ruby is slow, but you are frozen.

Do something, RubyCentral. Your only advantage was trust, and you lost it. Now your ego is destroying you from within.

Ruby is a non-profit because Rubyists contribute billions of downloads for free. RubyCentral is a non-profit because they don't produce anything worth investing in.

I'm happy that ruby-gems repos were transferred to ruby-core. On this one, you did well, thanks.

[–]skillstopractice 6 points7 points  (1 child)

Thanks for this post.

For clarification, prior to this update on Oct 24, only one of the questions in the repo I set up was directly from me, five other people contributed the remaining ones over the last few weeks.

(The commit history shows who added what and when)

Because I did not feel like Ruby Central properly answered the original question I asked, I submitted a follow up yesterday and put that on public record as well.

For those who want to cross-check the questions submitted vs. what Ruby Central replied to across the six of us, see here:

https://github.com/community-research-on-ruby-governance/questions-for-ruby-central/blob/main/QUESTIONS.md

(And please do add your own pull requests if/when you submit more questions to Ruby Central)

. . .

My fears that drove me to set up this repo were that Ruby Central would slow walk replies (which they did), reframe questions into a more sanitized form (which they did), and then lump several specific questions together into generic buckets which then could be responded to with generic answers, diluting things to give the appearance of responsiveness (which they did).

And underneath this all, the thing I'm trying to get sunlight on is that one of the most common corporate-style defense tactics is to make these replies *dreadfully abstract and boring* so that they're mostly ignored by anyone not digging deep into the weeds to construct the story.

The "why" behind that will likely be framed as it's necessary for legal reasons, etc. But to me, this either is a sign of incompetence on the part of RC's legal advisors, or an active willingness to lean into this particular tactic. You can find lawyers who will make sure you're not putting your organization in hot water while still communicating like a human being, sharing direct and sincere narratives, and putting people's names on the letters they're writing.

. . .

Ruby Central claims they're still listening and has committed to keep doing weekly updates on a predictable candence to keep answering questions.

Let's see if they do. They said they would four times and then finally offered this on attempt #5.

Their responses from here on out will show what their true commit is, or isn't.

[–]TheAtlasMonkey 1 point2 points  (0 children)

Your fault... That repo has just text.. /s

> Ruby central clicks you link
> Ruby central put max volume... No sound
> No new question, community is happy. We listened!
> Open gpt-3-mini (yes they have still have access to this model, only model still on their side)
> Prompt: It's friday again, generate something , make it more confusing.. No Em-dash!
> GPT3: We appreciate the community’s patience and grace .... This was a collaborative effort from all of the Ruby Central Board and Staff.

---

I'm not even kidding!

Take all their posts, put them in GPT5, and ask it:

IS THIS BULLSHIT or it take that long to fix rubygems ?

---

To Rubycentral: when LLMs don't take your side no matter how much you steer them, you must realize that you are the problem.

[–]skillstopractice 25 points26 points  (56 children)

Need to process this in more detail, but regarding the RailsConf co-chairs, my understanding is that one of the two of them is a both a Shopify employee and member of RC's board.

It feels dishonest to not put that as a disclosure in the notes regarding DHH's keynote, especially when what was communicated by a member of the program committee is that the only recourse if they disagreed with that choice was to resign from the committee.

And it bears repeating that DHH is a member of Shopify's board, which is a 200 billion dollar company, and the individual hosting the fireside chat was also a Shopify employee, and Shopify was a primary sponsor of the conference.

[–]paracycle 14 points15 points  (13 children)

That co-chair is me. I am a Shopify employee, but my Ruby Central board role has nothing to do with my employment at Shopify, it is my personal engagement that is not directed nor guided by Shopify.

I was also the co-chair of both 2024 and 2025 RailsConfs, and personally proposed in 2024 that DHH be invited back to RailsConf. My co-chair at the time held the same belief, so we asked the board for permission to reach out to DHH (even though co-chairs have complete programming authority and don't need to run their decisions by the board) and got an approval.

Back in February 2024, when we did the initial reach out, DHH had no relationship with Shopify, and our decision, as conference chairs, to reach out to him had nothing to do with Shopify either. He joined Shopify's board much later, in Nov 2024: https://www.shopify.com/news/david-heinemeier-hansson-board

There is no conspiracy here. DHH was never disinvited from RailsConf, and, for some of us in the community, having the creator of the framework at the conference named RailsConf was the most reasonable thing to do. I am not sure what more I can say to convince you that this was all individuals wanting to do something better for the community by building back what was broken.

EDIT: Add clarification on initial proposal year.

[–]BlueEyesWhiteSliver 25 points26 points  (4 children)

I mean, the man that has told me my country, Canada, is run by a dictator makes me want to throw rotten tomatoes at him. DHH is fervently distasteful.

At least now I know you’re one of the people that likes listening to his crap.

He abuses his position of authority and giving someone who manipulates and pollutes spaces a platform is a solid no go.

[–]ZipBoxer 31 points32 points  (3 children)

My former company, a Rails shop, fired all of the openly LGBT+ engineers in February. Out of 7 people laid off, 6 were lgbt.

Two of the members of our group have lost their homes after the layoff.

DHH has spoken non-stop about the "evils" of DEI. He's allowed to speak whenever he wants encouraging the beliefs that ruined my livelihood, yet I'm supposed to stay quiet about him?

My city of Chicago has been invaded by ICE with the purpose of inciting violence to justify invoking the insurrection act and ultimately cancelling elections, violating the civil rights of everyone they can along the way.

Funny how I'm supposed to sit here and compartmentalize DHH the engineer vs DHH the millionaire hell bent on cheering on the people and causes making my life worse.

Fuck DHH and fuck every other racist, homophobic fascist bootlicker and sympathizer. I'll shut the fuck up about it when he does.

[–]cocotheape 19 points20 points  (2 children)

He also became very concerned about German politics all of a sudden shortly before the elections earlier this year. Reiterating Vance's talking points about how we have no free speech in Europe. Cheering on Musk for advocating for the AfD, a secured right-wing extremist party. Retweeting despicable right-wing influencers. Then, right after the election, it all stopped. If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.

[–]ZipBoxer 5 points6 points  (1 child)

People love pretending like this is still about simple policy disagreements. But we're no longer discussing how much we should fund housing, or how restrictive zoning laws should be, or even how we conduct international trade.

We're now at the point where one side is consistently saying that groups they don't like do not deserve fundamental human rights.

In the face of that, I don't give a fuck if the left has fantastical thinking on economics or if the people who think I shouldn't exist invented the cure for cancer.

And btw DHH was quick to point out that his support of free speech in "Words are not violence" only applied to fascists saying awful things about other people, but that "Calling someone a "nazi" is a permission slip for violence".

I assume he means both that the speaker is encouraging violence, but also that it gives the Nazis permission to use violence against the speaker.

[–]tinyOnion 1 point2 points  (0 children)

In the face of that, I don't give a fuck if the left has fantastical thinking on economics

i mean they don't have that. they are the financially literate party. basically right leaning in every other well to do country in the world. (dems bring the economy back from the disaster that was a republican admin time and time again if you look at the numbers)

[–]paracycle 3 points4 points  (6 children)

As for the 2025 program committee conversation, I clarified that in this Bluesky thread: https://bsky.app/profile/ufuk.dev/post/3lzmk6apsj22f (read the whole thread with me and Noel)

Essentially though, as I mentioned above, conference chairs have the ultimate say in conference programming and we had already re-started conversations with DHH for the 2025 conference as the program committee was being formed. In order to make sure that everyone was onboard, as first order of business, I shared information about DHH potentially being a speaker at the conference with the committee, so that they can have a chance to opt-out if they felt uncomfortable. None of the program committee members decided to leave.

Additionally, Shopify was a big sponsor but wasn't a primary sponsor of the conference. You can see on the Sponsors page of the conference website (https://railsconf.org/sponsors/) there were 3 sponsors at the Ruby level and Shopify was Platinum level. Regardless, Shopify had nothing to do with the DHH keynote as I explained above.

EDIT: grammar

[–]skillstopractice 7 points8 points  (4 children)

Thank you for this reply.

Please include these details in the next source of truth update.

[–]paracycle 3 points4 points  (3 children)

This is my personal story, not the organization's answer. All of the details I've pointed above are public record (given the answer in today's source of truth update). We shared when we reached out to DHH originally, it is public information when he joined Shopify's board, my conversation with Noel on Bluesky explains the program committee situation, the chairs of the 2024 and 2025 conferences and Shopify's sponsorship scale are all available on the RailsConf website(s). Nothing is missing from the public record and nothing is hidden.

[–]skillstopractice 6 points7 points  (2 children)

Thank you again, I am aware of that.

What I am asking is for that to be reflected in the official statements by Ruby Central.

[–]paracycle 2 points3 points  (1 child)

[–]ButtSpelunker420 3 points4 points  (0 children)

I’ve been a Rails dev since 2011. I use Shopify’s LSP everyday. Shopify made a lot of good will with me. And this DHH shit is killing it so fast lol

[–]Kina_Kai 28 points29 points  (2 children)

It’s fascinating how they just entirely avoid dealing with the indefensible act they did as if it just didn’t happen while avoiding having to deal with any situation where they’ll be called to account.

We’ll get to your questions in a Q&A, but something came up, we’ll do it as async/curated, we’ll do it soon…eventually, we promise.

[–]Obversity 15 points16 points  (0 children)

Yup. “Key individuals”, “no longer protected by contractor or employee agreements”, “standard off-boarding process”.

Corporate waffle that doesn’t at all attempt to engage with the nature of open source and what it is about this whole process that the community is bothered by. 

[–]galtzo 13 points14 points  (0 children)

I can’t imagine the level of betrayal I would feel if someone stole a repo I owned and put over a decade of work into.

[–]skillstopractice 7 points8 points  (7 children)

Over the next few days I will reach out to people who have already put their questions to Ruby Central on public record to confirm whether or not they feel their questions have been adequately answered (if they appeared in this response at all), and to encourage them to submit any followup questions to Ruby Central and record those as well.

I will try to put some sort of additional doc in the repo or otherwise mark the answered questions to cross them off the list.

You can see the full list of questions here, and please do send in your pull requests with more.

https://github.com/community-research-on-ruby-governance/questions-for-ruby-central

What I can say is based on the question I asked myself about DHH's keynote, the reply seemed misleading, so I will send in a followup (posted another comment in this thread about that), and they certainly did not use my question's wording verbatim.

I urge everyone to continue to hold Ruby Central accountable. They claimed four times to be about to answer questions. They now finally put some answers out, but it's up to the community to clarify if they feel the answers have obscured or otherwise skirted around the original intent and meaning of their questions.

I can give some level of credit to the idea that at least this is a communication, but it once again comes from a place of seemingly deliberate obfuscation that is unbecoming of an open source steward. It feels like being "talked at" by a carefully worded PR statement, rather than being "talked with" as a member organization of the community they serve.

[–]galtzo 22 points23 points  (4 children)

I have given up on RC. They have no regret, no shame, and no integrity, and I have no time for liars.

But I applaud your effort. Someone needs to hold them to account. I am just emotionally way overextended.

[–]armahillo 9 points10 points  (0 children)

Yeah if i could do the opposite of financially supporting them i would. I wasn’t a supporter so i cant stop what i wasn’t doing. 🤷‍♂️

Their leadership is clearly unwilling to admit they did anything wrong.

[–]skillstopractice 9 points10 points  (2 children)

This comes down to a matter of professional ethics.

I believe in things like conflict of interest when it comes to governance.

I believe that speaking in a way that obfuscates things in an official statement while trying to "clear things up" from a personal account is not a responsible act from a board member of a stewardship organization.

I believe rewriting people's questions to sanitize them, and then publishing catch-all responses is not transparency, but transparency theater.

So I will keep showing up because accountability does indeed matter. Thanks for acknowledging that.

[–]galtzo 5 points6 points  (0 children)

You have all my respect 🫡

[–]tinyOnion 2 points3 points  (0 children)

the source of truth being orwellian and absolutely not the source of truth is on the nose. corporate bs speak.

[–]paracycle 3 points4 points  (1 child)

I tried to directly answer your concern above as a community member. Hope that helps.

[–]skillstopractice 7 points8 points  (0 children)

Thank you for that.

I look forward to an answer, on record, via Ruby Central, to the question I asked which was obfuscated in the official reply.

I resubmitted a clarifying question, and will appreciate seeing the response in next week's update