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.
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.
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
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 (rubycentral.org)