#rubycentral

The Quiet Work That Keeps Ruby Alive

I’ve written some critical things about Ruby Central. I’ve also written about choosing to contribute anyway, because the community matters more than the org chart. So when the January 2026 newsletter landed in my inbox, I read it with a specific question: is Ruby Central showing up for the people who make this ecosystem work?

The short answer: yes, in some meaningful ways.

The Gala Awards

Ruby Central is hosting a gala with awards that recognize the kinds of contributions that often go uncelebrated. And the honorees they’ve chosen say a lot about what the community values right now.

Ruby Heart Award — Emily Samp

The Ruby Heart Award honors extraordinary compassion and service to the community. Emily Samp is an Engineering Manager at Shopify, where she works on improving the Ruby development experience through open source tools like Sorbet and Prism. She’s also an organizer and co-founder of WNB.rb, and current CEO of the group.

That combination matters. Working on Sorbet and Prism makes every Ruby developer’s experience better. Co-founding WNB.rb makes sure “every Ruby developer” actually means everyone. She’s doing both at the same time, and that’s not an accident.

Ruby Guidepost Award — Saron Yitbarek

The Guidepost Award recognizes mentorship and guidance of the next generation, and Saron Yitbarek is the right person for it. Saron is the founder of CodeNewbie (now owned by DEV), a developer, speaker, and podcaster. I’ve had the pleasure of seeing her speak at RubyConf and NDC London.

If you’ve ever been new to programming and found a community that made you feel like you belonged, there’s a good chance Saron’s work had something to do with it. CodeNewbie created space for people who were just starting out, at a time when “beginner-friendly” wasn’t really a thing yet in tech.

Cutting Edge Award — Nadia Odunayo

The Cutting Edge Award goes to bold experimentation and boundary-pushing work. Nadia Odunayo founded The StoryGraph, a book-tracking app that has grown to over 4 million users as a privacy-focused alternative to Goodreads. I’m a huge fan.

And here’s the thing — The StoryGraph is built with Ruby. Millions of people use it every day who have no idea what Ruby is. That’s what pushing the boundaries of this ecosystem actually looks like.

Community Leadership Gem Award — You Decide

The one that caught my attention is the Community Leadership Gem Award, which is community-nominated. That matters. Letting the community choose who to celebrate instead of a board making that call from the top down is a small but meaningful shift toward the kind of governance I’ve been asking for.

If you know someone doing quiet, consistent work to make the Ruby community better, nominate them.

New Board Members

Three new members joined the Ruby Central board:

Brandon Weaver has been writing Ruby for 15 years and is known for his conference talks and education work. Having someone on the board who’s been in the trenches as a speaker and educator is good representation. He is good people, and will be pushing for communication and transparency with the board. No one knows Ruby like Brandon and I’m really excited to see what he does on the board.

Ran Craycraft is the Managing Director at thoughtbot. Thoughtbot has a long history of contributing to the Ruby ecosystem through open source and mentorship, so this feels like a natural fit.

Jey Flores leads Product Engineering at Code for America and previously worked at Bandcamp. Bringing in someone from the civic tech space broadens the perspective on who Ruby serves and how.

The RubyGems situation showed what happens when leadership stops listening to the people doing the work. Fresh voices on the board could help with that.

WNB.rb and the Volunteers Who Build Community

This is the part of the newsletter that I love is called out but heads up that I’m biased when it comes to WNB.rb. I’ve been a member of the community since it was founded and have joined up on WNB.rb’s board. So the community means a lot to me, and I am so happy it is being shared in the newsletter.

WNB.rb (Women and Non-Binary Rubyists) group is transitioning from a founder-led organization to a community-managed one. That’s hard work, and it’s how you make something last.

The newsletter highlights two people by name:

Sarah Eggleston, WNB.rb’s Deputy CTO, who’s helped grow the community and make it a place people actually want to show up to. And Jess Sullivan, the Book Club Lead, who makes it okay to not know things yet. Both amazing people, who care deeply about Ruby and WNB.rb.

That last part is worth sitting with. Jess is normalizing imperfect learning. That doesn’t show up on a GitHub contribution graph, but it changes how people experience this community.

WNB.rb’s mission of making the Ruby community accessible to marginalized individuals entering tech is worth paying attention to. If you’re not already involved, look into it and support the mission.

Looking Ahead

The newsletter also covers some forward-looking items worth noting:

  • RubyConf 2026 is heading to Red Rock, Nevada, with a new “Ruby Runway” pitch competition for Ruby-based projects
  • RubyGems.org Organizations is in private beta, adding multi-maintainer gem management (a feature that directly addresses some of the collaboration pain points I’ve seen firsthand)
  • Google Summer of Code is looking for Ruby projects and mentors, with a focus on AI/ML and security

What This Means

Governance issues don’t resolve in a few months, and trust takes time to rebuild. But spotlighting community volunteers by name, letting the community nominate its own awards, bringing in new board members, that’s Ruby Central showing that it knows the community matters. I’m really liking what I’m seeing with the continued communication.

The newsletter discussed in this post: Ruby Central README: January 2026

#community #ruby #rubycentral
|7eter l-|. l3oling 🧰galtzo@ruby.social
2026-02-06

My thoughts on the RubyGems hostile takeover of September 2025, and what I'm doing about it. #Ruby #RubyGems #RubyCentral #Governance :ruby: :jruby: :truffleruby:
dev.to/galtzo/hostile-takeover

2025-11-03

"I am concerned that Ruby Central’s board with full knowledge of the consequences and the alternatives voted to take over a collection of open source projects from their maintainers without consent. Especially when these maintainers were acting in good faith at the time. This is the organisation we are meant to trust to host our Ruby gems."

#JoelDrapper, September, 2025

joel.drapper.me/p/rubygems-tak

If what Joel describes here is true, this is deeply fucked.

#Ruby #RubyCentral #RubyGems #Shopify

|7eter l-|. l3oling 🧰galtzo@ruby.social
2025-10-25

"Deprecate bundler is in the pipeline"

Interesting. It seemed they they took offense at Arko working on a bundler alternative, but apparently they were already planning to deprecate bundler? So why is there any concern about people working on alternatives?

#ruby :ruby: #rubycentral

NOTE: This was a very hard watch, and I was mentally exhausted by the end of it.

youtu.be/nKpo68g9dEk?si=E9XWI1

2025-10-24

@rubycentral The video from Technology for Humans Podcast is truly remarkable and a must-see.

The link is missing in this update, so I'm posting it here:

Technology for Humans: Shan Cureton
(published today, October 25)

Thanks to Ruby Central for this in-depth update ❤️

youtube.com/watch?v=nKpo68g9dE

#ruby #rubycentral

With a not-too heavy heart I now cancelled my (financial) support of #RubyCentral.
I'm sure this won't hurt their finances significantly. I firmly believe Shopify's contributions are/were MUCH bigger than mine.

Note that I still very much love #Ruby, the language! 💖 — Rubycentral not so much, though.

#Ruby

2025-10-11

Don’t be a #scab. #rubygems needs maintainers and on call support due to @rubycentral’s own actions. Stepping in now is no different than crossing a picket line. Just don’t do it

#ruby #rails #rubycentral

Ziggy the Hamster ☎️ 4ZTHZiggyTheHamster@ruby.social
2025-10-09

Like... did the probable person responsible take over the account to use as leverage (the subtext #RubyCentral is implying), or did they act prudently to maintain control of an account they otherwise were stewards of?

If I presume the probable person is as reasonable as they appear to be, then malice seems totally out of character. So why paint them as a villain? Why mention Joel's blog post at all if not to sling shit at Joel?

We're better than this sort of thing, come on.

N-gated Hacker Newsngate
2025-10-09

🎭 Oh, look! It's Ruby Central's riveting recount of a 2025 slip-up where someone forgot to revoke access, giving a former maintainer the keys to the kingdom. 🎉 But fear not, they've published a post-incident that's about as exciting as watching paint dry, with a thrilling promise to maybe, just maybe, not let it happen again. 🔒🔑
rubycentral.org/news/rubygems-

2025-10-08

@rubycentral is really going with the “stay quiet until it all blows over” approach. They’ve completely stopped communicating with their community, no toots, no empty corporate statements, no question and answer sessions.

Why do they think this is the way to repair the damage?

#ruby #rails #rubycentral #rubygems

2025-10-07

Between #rubycentral, #rubyonrails dramas and #cocapods closing it's must be quite the time to be a #ruby dev

2025-10-06

The prospect of fashy RubyGems.org/Ruby Central getting displaced by a literal coop with a .coop domain name ( gem.coop ) is beyond entertaining for me. I am so excited. LFG

#ruby #RubyGems #RubyCentral #GemCoop

PointlessOne :loading:pointlessone@status.pointless.one
2025-10-03

I see people working on alternatives to rubygems.org.

I don't know all the initiatives but one of the proposals is to set up an alternative gem index. With tiered access and higher tiers are paid and are supposed to finance the operation.

I'm glad people are organisig and doing something. But I think this is ultimately a wrong approach.

First, a simple caching proxy (such as Artifactory) can easily alleviate the need for a higher tier access to the index. And most big orgs already have something like that in place so won't even need additional effort.

Second, a centralised index is subject to all the same issues that befell rubygems.org. It's expensive, requiring some sort of financing on a regular basis. Eventually this might result in the very same issue: either become dependent to corporate interests, or shutdown. Tiered access might also be detrimental for mirroring which may or may not be desirable.

I suggest we should go distributed. Every project should host their gems wherever. Do you have a domain associated with your project where you host it's web site/docs? Host the gems there as well. See `gem generate_index`. Do you host your code on Codeberg/Forgejo? It also can host gems.

I'm not very concerned about gem hosting. We already have tools to do that without rubygems.org.

My bigger concern is that the tools are under… let's say, uncertain control.

RubyGems (the CLI) and bundler are under RC control. The repos can be forked and other people can work on them but, I'm afraid, that doesn't matter. Ruby (the language) bundles both rubygems and bundler. Can we convince Ruby maintainers to use a version that is not under RC control? I doubt. Given that HSBT is on the Ruby Core team, and he was instrumental in the takeover, and that there was no concern voiced by anyone else from Ruby Core team, I take it this move is supported by the Ruby Core.

I'm afraid that any effort to take the development back to the community is futile because of this.

I suspect that for a while all the projects will keep accepting contributions from the community, and will keep insisting they're for the community benefit. But eventually there will be some change that goes against the community interests but is requested by some corporate backer and RC will show their chosen side again. All community concerns will be ignored and the change will be implemented anyway.

My concern is that Ruby transitions from a community, a diverse network of projects to an openly extractive ecosystem. A few wealthy corporations fully control the development of the technology and extract existing value, ride the inertia of the community.

This is a natural progression of every technology. Enthusiasts go elsewhere as the technology stagnates and new shiny things appear, while big corpo stays as it's expensive to migrate away. They become the only benefactors, and effectively, supporters of the technology. And since there's not much interest anyway they can stir it wherever they want.

This certainly was happening with Ruby for a while. The concern that Rails is the major use case for Ruby was around for years. New alternative technologies appear and mature so there are places for people to go, while Ruby has not found new niches to expand to.

RC takeover of rubygems/bundler greatly accelerated this natural process. Whether there was corporate pressure, a prominent figure in leadership ego burst, a malicious intent, or a fumbled attempt at stewardship backed by the best intentions, either way the community is effectively removed from the tools development. Maybe not completely but I find surprising (mostly) silent agreement between RC, Rails Core, and Ruby Core. Basically all technical leadership of the most prominent parts of the Ruby ecosystem are perfectly aligned between themselves even when there's a great deal of concern and uncertainty in the community.

#Ruby #RubyGems #bundler #RubyCentral #RubyOnRails

|7eter l-|. l3oling 🧰galtzo@ruby.social
2025-10-03

@ShadSterling @quintasan Find the new invite link in this PR!!
github.com/rubygems/bundler-si
:ruby: 💎 We're discussing ideas on the future of the RubyGems.org alternative. #Ruby #RubyCentral

2025-10-01

The bullshit-o-meter is going off the charts!

It certainly looks like #RubyCentral is absolutely in full damage control mode now, since this post:

- Reads like corporate bullshit;
- Tries hard as fuck to avoid the elephant in the room that is the loss of trust they caused;
- Tries to gaslight us by stating "this is not a takeover" as fact, while everyone can see it is a takeover.

rubycentral.org/news/our-stewa

#ruby #rubygems #foss

Esparta :ruby:esparta@ruby.social
2025-10-01

@rubycentral
Continuing with #SFRuby meeting for September 2025.

... and here we are with André Arko (Spinel Coop) @indirect who will be taking about rv, a New Kind of Ruby Management Tool

- rv is made with #rust
- is based on portable-ruby, from Homebrew

Note: André was book for this meeting way before the #rubycentral fiasco in the #ruby community

#SFRuby #sfba

André Arko (Spinel Coop) @indirect@fiasco.social who will be taking about rv, a New Kind of Ruby Management ToolAndré Arko (Spinel Coop) @indirect@fiasco.social who will be taking about rv, a New Kind of Ruby Management ToolAndré Arko (Spinel Coop) @indirect@fiasco.social who will be taking about rv, a New Kind of Ruby Management ToolAndré Arko (Spinel Coop) @indirect@fiasco.social who will be taking about rv, a New Kind of Ruby Management Tool
Esparta :ruby:esparta@ruby.social
2025-10-01

Continuing with #SFRuby meeting for September 2025

A note from Irina about the elephant in the room

> We're amist a major conflict... @rubycentral

#SFRuby #ruby #sfba #rubycentral

Irina talking about the #rubycentral fiasco:

> We're amidst a major conflict (#rubygems)

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst