Richard Schneeman6d ago

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
Show threadAaron
@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.
Mar 31 at 5:41pmIvory for Mac
Show threadPointlessOne 6d 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 threadsoc6d ago
@harpaa01 🤡