Ruby Central's Destructive Legacy
Ruby Central, a non-profit organization, has been involved in a dispute over the control of open-source projects such as Bundler and RubyGems. The organization has lost several conferences, contributors, and sponsors, and has been accused of a hostile takeover of the projects. The dispute remains unresolved, with Ruby Central threatening to sue one of the maintainers of the projects.
- ▪Ruby Central has lost 2 of 2 conferences and 2 of 3 major open-source projects.
- ▪The organization has lost 9 of 10 contributors to open-source work and 5 of 7 board members.
- ▪Ruby Central has added a new security project, funded by a grant from Alpha-Omega, but has been criticized for a conflict of interest in its sponsorship drive.
Hacker News (Front Page) files mainly under programming. We currently carry 868 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | André.Arko.net |
| Canonical URL | https://andre.arko.net/2026/07/30/ruby-centrals-destructive-legacy/ |
| Publication time | Fri, 31 Jul 2026 12:10:55 +0000 |
| Retrieval time | 2026-07-31T12:37:49.360Z |
| Last seen | 2026-07-31T12:37:49.360Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | DTAalRRIuToi · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
30 Jul 2026Ruby Central's Destructive LegacyAt 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.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at André.Arko.net.
Discussion
0 commentsMore from André.Arko.net
