Post #1180309
2026-03-31 14:16 UTC
Replies (5)
-
@harpaa01@mastodon.social 2026-03-31 17:41
@Schneems@ruby.social 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.
-
@Schneems@ruby.social 2026-03-31 14:18
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.
-
@soulcutter@ruby.social 2026-03-31 14:54
@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”?
-
@kuba@ruby.social 2026-03-31 15:55
@Schneems thank You very much Richard for creating this post mortem!
-
@pointlessone@status.pointless.one 2026-03-31 16:04
@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?