Seth A. Roby3d ago
Richard Schneeman

I joined RubyCentral to release a postmortem, and today I'm delivering my report on what happened. The hope is to provide more transparency and closure, 194 days since the incident on September 18, 2025.

I've named the incident "RubyGems Fracture." For full details, read my report. #ruby

https://rubycentral.org/news/rubygems-fracture-incident-report/

RubyGems Fracture Incident Report

By: Richard Schneeman This document attempts to give closure to the Ruby community about the events that led to the incident, September 10-18, 2025, which I’ve named “RubyGems Fracture.” Preamble I joined Ruby Central’s Open Source Committee on October 22nd, 2025, after the GitHub access changes. I was

Ruby Central
Mar 31 at 2:16pmWeb
Show threadRichard Schneeman4d ago

I previously wrote this on how you can hold me accountable in this work https://ruby.social/@Schneems/116216591665738708.

Though I'll probably be slow to respond today.

Show threadBradley Schaefer4d ago

@Schneems thanks you for writing this.

I have a couple more questions.

Give the connection between github access and the production system, why wasn’t that addressed directly by taking technical measures to separate that? It seems like that’s where RC feels like they own the org, and from many peoples’ POVs they don’t.

Given that connection, how does it make sense to pass org ownership to Matz / Ruby Core?

If this was a legal thing about Andre/logs, why not send him a legal notice “don’t”?

Show threadBradley Schaefer4d ago
@Schneems This doesn’t change my viewpoint much about what happened, but is the most transparency we’ve gotten from RC about the fracture, thank you for that.
Show threadKuba =)K4d ago
@Schneems thank You very much Richard for creating this post mortem!
Show threadPointlessOne 4d ago

@Schneems First of all, thank you for the report.

It does provide some additional clarity but not much closure.

For one, even though you speak for the organisation, it's only you speaking. People who were directly involved and made the mistakes did not come forward so far. And even then it's only admission of mistakes. There’s not even a symbolic apology. But also apparently no concrete plans to change anything.

Another thing not covered here is how rubygems ended up in ruby org. What’s RC's ivolvement with it now?

Show threadAaron4d ago
@Schneems I nominate you to be in charge of all comms coming out of RC moving forward. This provides a level of clarity and transparency that should be the standard.
Show threadPointlessOne 4d ago

@harpaa01 I don't think this level is tenable in the moment. It's a decent report and right changes can be made based on it but I think this is impossible in real-time as the situation unfolds.

@Schneems

Show threadsoc4d ago
@harpaa01 🤡