
CommunityNews
Ruby Central's Attack on RubyGems
Hi! I’m Ellen, but you probably know me as duckinator or puppy.
I really wish I didn’t have to write this, but I feel the Ruby community needs to know it.
I have been part of the Ruby community since I was 13, and one of the RubyGems
maintainers for the last decade.
This community has helped me through very hard times, and you mean the world to me.
One of the most important lessons I learned from y’all is this:
A person’s character is determined not only by their actions,
but also the actions they stay silent while witnessing.
This Month Has Been A Fuck Of A Year
Read in full here:
Most Liked

alvinkatojr
What a pathetically insensitive response to a wanton betrayal of trust to members of the community. But then again, that’s how most corpos run. Once something is steady and running, they’ll jump in and seize it, cut off all opposition, then run and hide behind legal jargon and fiduciary duties.
Thanks for sharing the response @AstonJ. The Ruby community is prone to these kinds of fights. Sometime back RubyTogether and DHH got into it. It’s baffling.
To any future language designer, make sure you create and own the package repository for any libraries created using your language. We’ve seen enough of these fights and we are tired.

AstonJ
I’m not sure tbh, generally the more professional an outfit is the less they want to be drawn into drama. This is a policy I share as generally we only get into details (for instance, of member mishaps) if we feel we are left with little other choice. Sometimes this level of professionalism is taken advantage of, which can then lead to people feeling like they can embellish things - and at that point then you have to step in. I guess that’s what this board member felt they had to do with this latest blog post:

alvinkatojr
I agree with this stance and you too on this matter. Most importantly, after reading Freedom Dumlao’s perspective, I’ve had a change of heart and do agree with the decision taken by Ruby Central. But I still disagree with their response, which lacked any empathy from a human perspective and the way they went about it.
As per Ellen’s side, sometimes we get so involved in a project, team, company and we forget that there is the business side. And the business side is cold, unemotional and brutal. I feel for her, but this was strictly a business move. Hopefully, she moves on and gets the closure she needs.
We can’t prevent all blowups(and I’m speaking as someone who’s been the cause of a couple here on this very forum and a couple others), but we can at least prevent them from turning massive or emotional. This in my view, was Ruby Central’s biggest failure.
Thankfully, a board member came to their rescue and shed more light, but the lesson still rings true: prevention is better than cure.
Popular Backend topics









Other popular topics










Categories:
Sub Categories:
Popular Portals
- /elixir
- /rust
- /ruby
- /wasm
- /erlang
- /phoenix
- /keyboards
- /rails
- /python
- /js
- /security
- /go
- /swift
- /vim
- /clojure
- /emacs
- /haskell
- /java
- /onivim
- /svelte
- /typescript
- /kotlin
- /c-plus-plus
- /crystal
- /tailwind
- /react
- /gleam
- /ocaml
- /flutter
- /elm
- /vscode
- /ash
- /html
- /opensuse
- /centos
- /php
- /deepseek
- /zig
- /scala
- /textmate
- /lisp
- /sublime-text
- /nixos
- /debian
- /react-native
- /agda
- /kubuntu
- /arch-linux
- /django
- /ubuntu
- /revery
- /manjaro
- /spring
- /nodejs
- /diversity
- /deno
- /lua
- /julia
- /slackware
- /c