Skip to content
Tech News
← Back to articles

Ruby Central's Destructive Legacy

read original more articles
Why This Matters

The controversy surrounding Ruby Central's takeover of key Ruby open-source projects highlights ongoing governance and community trust issues within the Ruby ecosystem. This situation underscores the importance of transparent leadership and community involvement in open-source development, which directly impacts developers and users relying on these tools. Addressing these conflicts is crucial for maintaining a healthy, collaborative open-source environment that benefits the broader tech industry.

Key Takeaways

Ruby Central's Destructive Legacy

At conferences and meetups, and in conversations online, many Ruby developers have asked me about Ruby Central and my disagreement with them. This post is my attempt to answer the questions I’ve been getting over and over, covering: 1) what is Ruby Central doing now? 2) has the dispute over Bundler and RubyGems been resolved? 3) what has Ruby Central said about the dispute? and 4) what can Ruby developers do now?

What is Ruby Central doing now?

To talk about what Ruby Central is doing now, we need to start with a bit of historical context. What was Ruby Central doing before this saga began? About 18 months ago, Ruby Central:

ran 2 conferences every year, RubyConf and RailsConf

had an Open Source Committee with 3 members (Ufuk, Gabi, Mike)

funded 7 part-time community OSS contributors (André, Arun, Ellen, Gift, Irene, Josef, Martin)

funded 3 full-time OSS developers (Colby, Samuel, David)

coordinated those 10 OSS contributors across 3 major OSS projects: RubyGems Bundler RubyGems.org

... continue reading