<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[I joined RubyCentral to release a postmortem, and today I&#x27;m delivering my report on what happened.]]></title><description><![CDATA[<p>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.</p><p>I've named the incident "RubyGems Fracture." For full details, read my report. <a href="https://ruby.social/tags/ruby" rel="tag">#<span>ruby</span></a></p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://rubycentral.org/news/rubygems-fracture-incident-report/" title="RubyGems Fracture Incident Report">
<img src="https://rubycentral.org/content/images/2024/04/Ruby-Central-OpenGraph-1.png" class="card-img-top not-responsive" style="max-height: 15rem;" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a href="https://rubycentral.org/news/rubygems-fracture-incident-report/">
RubyGems Fracture Incident Report
</a>
</h5>
<p class="card-text line-clamp-3">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</p>
</div>
<a href="https://rubycentral.org/news/rubygems-fracture-incident-report/" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://rubycentral.org/content/images/size/w256h256/format/png/2022/11/Ruby-Central-logo.svg" alt="favicon" class="not-responsive overflow-hiddden" style="max-width: 21px; max-height: 21px;" />





<p class="d-inline-block text-truncate mb-0">Ruby Central <span class="text-secondary">(rubycentral.org)</span></p>
</a>
</div></p>]]></description><link>https://board.circlewithadot.net/topic/d5b6e987-6be6-406b-8405-0c566e42113e/i-joined-rubycentral-to-release-a-postmortem-and-today-i-m-delivering-my-report-on-what-happened.</link><generator>RSS for Node</generator><lastBuildDate>Mon, 06 Apr 2026 07:58:39 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/d5b6e987-6be6-406b-8405-0c566e42113e.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 31 Mar 2026 14:16:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to I joined RubyCentral to release a postmortem, and today I&#x27;m delivering my report on what happened. on Tue, 31 Mar 2026 16:04:59 GMT]]></title><description><![CDATA[<p><span><a href="/user/schneems%40ruby.social" rel="nofollow noopener">@<span>Schneems</span></a></span> First of all, thank you for the report.</p><p>It does provide some additional clarity but not much closure.</p><p>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.</p><p>Another thing not covered here is how rubygems ended up in ruby org. What’s RC's ivolvement with it now?</p>]]></description><link>https://board.circlewithadot.net/post/https://status.pointless.one/users/pointlessone/statuses/116324637024573682</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://status.pointless.one/users/pointlessone/statuses/116324637024573682</guid><dc:creator><![CDATA[pointlessone@status.pointless.one]]></dc:creator><pubDate>Tue, 31 Mar 2026 16:04:59 GMT</pubDate></item><item><title><![CDATA[Reply to I joined RubyCentral to release a postmortem, and today I&#x27;m delivering my report on what happened. on Tue, 31 Mar 2026 15:55:20 GMT]]></title><description><![CDATA[<p><span><a href="/user/schneems%40ruby.social">@<span>Schneems</span></a></span> thank You very much Richard for creating this post mortem!</p>]]></description><link>https://board.circlewithadot.net/post/https://ruby.social/users/kuba/statuses/116324599102328187</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://ruby.social/users/kuba/statuses/116324599102328187</guid><dc:creator><![CDATA[kuba@ruby.social]]></dc:creator><pubDate>Tue, 31 Mar 2026 15:55:20 GMT</pubDate></item><item><title><![CDATA[Reply to I joined RubyCentral to release a postmortem, and today I&#x27;m delivering my report on what happened. on Tue, 31 Mar 2026 15:15:21 GMT]]></title><description><![CDATA[<p><span><a href="/user/schneems%40ruby.social">@<span>Schneems</span></a></span> 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.</p>]]></description><link>https://board.circlewithadot.net/post/https://ruby.social/users/soulcutter/statuses/116324441875015506</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://ruby.social/users/soulcutter/statuses/116324441875015506</guid><dc:creator><![CDATA[soulcutter@ruby.social]]></dc:creator><pubDate>Tue, 31 Mar 2026 15:15:21 GMT</pubDate></item><item><title><![CDATA[Reply to I joined RubyCentral to release a postmortem, and today I&#x27;m delivering my report on what happened. on Tue, 31 Mar 2026 14:54:59 GMT]]></title><description><![CDATA[<p><span><a href="/user/schneems%40ruby.social">@<span>Schneems</span></a></span> thanks you for writing this.</p><p>I have a couple more questions.</p><p>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.</p><p>Given that connection, how does it make sense to pass org ownership to Matz / Ruby Core? </p><p>If this was a legal thing about Andre/logs, why not send him a legal notice “don’t”?</p>]]></description><link>https://board.circlewithadot.net/post/https://ruby.social/users/soulcutter/statuses/116324361778338060</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://ruby.social/users/soulcutter/statuses/116324361778338060</guid><dc:creator><![CDATA[soulcutter@ruby.social]]></dc:creator><pubDate>Tue, 31 Mar 2026 14:54:59 GMT</pubDate></item><item><title><![CDATA[Reply to I joined RubyCentral to release a postmortem, and today I&#x27;m delivering my report on what happened. on Tue, 31 Mar 2026 14:18:36 GMT]]></title><description><![CDATA[<p>I previously wrote this on how you can hold me accountable in this work <a href="https://ruby.social/@Schneems/116216591665738708" rel="nofollow noopener"><span>https://</span><span>ruby.social/@Schneems/11621659</span><span>1665738708</span></a>. </p><p>Though I'll probably be slow to respond today.</p>]]></description><link>https://board.circlewithadot.net/post/https://ruby.social/users/Schneems/statuses/116324218751819984</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://ruby.social/users/Schneems/statuses/116324218751819984</guid><dc:creator><![CDATA[schneems@ruby.social]]></dc:creator><pubDate>Tue, 31 Mar 2026 14:18:36 GMT</pubDate></item></channel></rss>