Sharing my toolkit for how I debug my computer in the morning before I get to work on @beautifulruby.com. youtu.be/tv3BTKgz2uY

I completely agree that they really care, but they allowed communication to atrophy so significantly that they felt they couldn’t even talk to anyone (just look at how the board thinks maintainers will react to reasonable security measures). Literally no one at RC ever reached out to me about this.

Matz is sponsored so we are sponsored

Bundler belongs to the Ruby community andre.arko.net/2025/09/25/b...

I agree and even more so: what if the problem is us, the Ruby community, not contributing to our key nonprofit enough? We did not have ownership because we didn’t show up, and RC ended up being squeezed by a big donor because they did not have enough sponsors, stability and support.

The events of the past week have still been really hard for me to process. The only way I can describe it is a nasty breakup of a decade-long relationship. I know people in the community are (rightfully) upset. I just ask that you remember individuals were directly hurt too.

Go read @rhiannon.io’s take. I was just wishing you were still there to smooth the relations. Now even more so after reading your balanced yet inspiring take on the situation. Go read this whole thread.

Then open things up. Bring sponsors to the table. Bring community members to the table. Bring maintainers to the table (if they’re willing to join) and discuss what next steps could look like if we collectively built the future the ecosystem needs and deserves.

For RC, why *not* use this as a moment to step back and say, okay, whatever actually happened, whatever our intentions, we’ve gone off the rails (lol) — community trust is lost, we’re not operating in a way that is in line with open source values… This is a wake up call. Let’s own this.

This doesn’t have to be a travesty for the ecosystem. Fundamentally I think *everyone* wants Ruby to continue to grow and thrive and be secure and get adopted by more companies and have more diverse funding sources. There has to be a path where this can end up being a good outcome.

In the last 2 weeks I’ve gone from knowing very little about Homebrew and how they run, to being absolutely fascinated by it and wanting to contribute. It’s one bright star in this situation that may never have happened otherwise. Thanks @mikemcquaid.com. docs.brew.sh/Homebrew-Gov...

I love your approach @mikemcquaid.com. I think this data shows a lot, but as you said there’s some hidden stuff too, so no one should run with this as the definitive list of rightful maintainers. It’s a great start though and I’d be happy to use and build on this. Better than gut feelings.

As I was saying…

Simi just wrote up an announcement that he’s done cooperating RubyCentral and it’s another very important read in this whole situation. Notably, he confirms everything in Joel Drapper’s write-up that’s already been circulating and really puts Ruby Central on blast.

Hullo hobbits! Tracking is now working on theburrowbook.com (Tales of the Shire Companion App)! Now you can track your hooked fish and cooked meals. #talesoftheshire

We'll need to learn things like: - Is kicking off agents parallel actually worth it? (Does it feel more productive, or is it actually?) - For what type of work is this worthwhile? (Even if it works, won't be a fit for everything!) - When is it not worth it? Etc

Until now, programming was a "single-threaded" activity. As a dev, I'd get "in the zone" and get it done. AI agents change this: you can now kick off parallel coding tasks. I see more devs do this... and this feels like brand new territory. We'll need to learn. A lot!

Joel did an amazing amount of investigative work to put together the most accurate representation of this situation that I’m aware of. I stand by everything that I’m able to vouch for. I don’t have anything else to add. Thank you for your effort here @joel.drapper.me

After listening to about a dozen first-hand accounts, I’ve published what I know about the RubyGems takeover.

Autistic folks are _heavily_ represented in STEM fields, so it would be far more accurate to say: Autism causes vaccines.

I share your perspective. As I watched Shan’s video I was saying, “yes, sure, operator agreements, seems fine… one flaw, you drew the circle around what you own wrong.” The reason I proposed governance is that I agreed we had ambiguity, as Shan also said about the merger docs. A coup isn’t the fix

The Tylenol only makes my autism more powerful, and with the number of migraines I get a year there'll be no stopping me!

I deleted my previous posting on the Rubygems situation as it was conjecture based on back channel rumors. I want to assume good faith from Ruby Central so I’ll shut up, learn from this mistake and let the primary parties tell their own story.

Wow, I may be late to the party but K-Pop Demon Hunters is so good!

I really appreciate your post @apiguy.dev. Thank you for posting your thoughts. I wish you had the info I had to make your decision. Here's the core issue: Before Sept 9, when a trusted maintainer broke our shared contract and added an RC non-maintainer, you had no ability to enact your vote.

What’s the value of owning the place where open source lives? code can be forked maintainers can leave users can abandon Then what lives in the repositories? Trust. Trust lives there, but only if everyone agrees. If you destroy trust to become owner, then what do you own? A kingdom of ashes.

To me, there is a difference between being nice and being kind. Being nice is avoiding confrontation and keeping the peace. Being kind is grabbing your friend by the shoulders and telling them how they fucked up, and what they need to do to make it right. When being nice fails, be kind.

Today has been... intense. Thank you everyone who's discussed this with me and offered kind words or support. I don't know the intent behind what happened. The people involved aren't villains, and they aren't evil.

Having met with both sides on the current RubyCentral/RubyGems situation, here's my take: - RubyCentral have managed this exceptionally poorly in many ways including removing literally the most active member of the RubyGems organisation by mistake who has declined to return

Hey, #ruby folks! I've been one of the #RubyGems maintainers for the last decade. Ruby Central has forcefully taken control of the RubyGems organization on GitHub, the `rubygems-update` and `bundler` gems on rubygems[.]org, and more. You can read the details here: pup-e.com/goodbye-ruby...

oof, what a disappointing way to end more than 15 years of open source work. (summary by @duckinator.bsky.social at pup-e.com/goodbye-ruby...). good luck to the remaining RubyGems team, and it’s time to focus my energy on new projects that I’m truly excited about, like rv.dev

do you like learning about how to accidentally delete your production database? I just gave a talk at @friendlyrb.com about how SQLite creates new ways to cause outages, and you can read the blog post version here andre.arko.net/2025/09/11/r...

When I made MDPhlex I didn’t realize Rails 8.1 was adding native `to_markdown` convention. Make organized Markdown (like /llms.txt) generation easy with MDPhlex and Phlex components. github.com/martinemde/m...

🛎️ Bright Sunny `STUDIO` 🌞 – $0/mo Turn any CLI command into a one-room MCP server. Clean, compact. Move-in ready. `gem install studio` 🔗 github.com/martinemde/s...

I made a new ruby gem that implements JSON-RPC protocol. The intention was to create a foundation for Ruby Model Context Protocol. I noticed that Ruby MCP implementations seemed to struggle with reimplementing JSON-RPC. Now you can offload it to my reimplementation! github.com/martinemde/p...