I'm looking for a job, and/or sponsorships for my open source work (mostly #ruby). My daughter has congenital heart disease, and there is no way I could afford her care without insurance. I am grateful for those who already contribute. I currently make 10% of the monthly cost of the health insurance premium, so please contribute monthly if you can. #getfedihired https://github.com/sponsors/pboling
I'm looking for a job, and/or sponsorships for my open source work (mostly #ruby). My daughter has congenital heart disease, and there is no way I could afford her care without insurance. I am grateful for those who already contribute. I currently make 10% of the monthly cost of the health insurance premium, so please contribute monthly if you can. #getfedihired https://github.com/sponsors/pboling
I am currently working to improve the state of  #SBOM (Software Bill of Materials) libraries and compliance in Ruby. SBOMs have been required by the US government since 2023, but  #ruby has been slow to catch on.
https://github.com/CycloneDX/cyclonedx-ruby-gem/pull/38
I'm looking for a job, and/or sponsorships for my open source work (mostly #ruby). My daughter has congenital heart disease, and there is no way I could afford her care without insurance. I am grateful for those who already contribute. I currently make 10% of the monthly cost of the health insurance premium, so please contribute monthly if you can. #getfedihired https://github.com/sponsors/pboling
A good summary of the Rubygems hostile takeover
My team is looking to hire an experienced #Ruby engineer https://lnkd.in/dWm2R-YG
The job's 100% remote, the team's really great and we’re working on several quite diverse projects. So, why not join us? :-)
My team is looking to hire an experienced #Ruby engineer https://lnkd.in/dWm2R-YG
The job's 100% remote, the team's really great and we’re working on several quite diverse projects. So, why not join us? :-)
 #Ruby's  #Float contains interesting constants.
  #Ruby's  #Float contains interesting constants.
Like EPSILON, which is the
> difference between 1 and the smallest double-precision floating point number greater than 1.
What is it useful for, you ask?
Well, Floats are kinda difficult for computers and if you want to compare them for equality without using `round` or alike, you can check whether its difference is within EPSILON range.
So it is kinda close to how Math uses it (ε).
It's hard not to see the huge upswell of community support for #Python and the @ThePSF and not feel sadly vindicated in recent criticism of the state of the #Ruby community.
Python is unbelievably popular, shed its outdated BDFL model years ago and built better governance, and has found broad application across dozens of vertical industries.
Ruby barely holds above legacy language water (Objective-C, Groovy), offers one big (fashy) framework, and governance is objectively in disarray.
We want to move Ruby forward / André Arko
「 To bring this about, we are prepared to transfer our interests in RubyGems and Bundler to Matz, end the dispute over the GitHub enterprise account, 2 GitHub organizations, and 70 repositories, and hand over all rights in the Bundler logo and Bundler name, including the trademark applications in the US, EU, and Japan 」
https://andre.arko.net/2025/10/26/we-want-to-move-ruby-forward/
We want to move Ruby forward
 
      
  
            We want to move Ruby forward / André Arko
「 To bring this about, we are prepared to transfer our interests in RubyGems and Bundler to Matz, end the dispute over the GitHub enterprise account, 2 GitHub organizations, and 70 repositories, and hand over all rights in the Bundler logo and Bundler name, including the trademark applications in the US, EU, and Japan 」
https://andre.arko.net/2025/10/26/we-want-to-move-ruby-forward/
We want to move Ruby forward
 
      
  
            Andrea @afomera is good people. She's as passionate as they come for #Ruby. You want her on your team. And it's a damn shame there are a handful of noisy people who are too blinded by their own ignorance to see that.
It's a reminder we must redouble our efforts to ensure the tech community, and our little corner of it in particular, are welcoming and affirming of everyone. We can start here. ❤️🧡💛💚💙💜
https://afomera.dev/posts/2025-10-25-stop-giving-harm-a-microphone
@getajobmike @afomera It really hit home how much we need to actually do a plan vert. Lots of projects fork, and its fine. Is there a discussion happening in some secret cave somewhere on how to go about it? #Ruby #planvert #rails
Andrea @afomera is good people. She's as passionate as they come for #Ruby. You want her on your team. And it's a damn shame there are a handful of noisy people who are too blinded by their own ignorance to see that.
It's a reminder we must redouble our efforts to ensure the tech community, and our little corner of it in particular, are welcoming and affirming of everyone. We can start here. ❤️🧡💛💚💙💜
https://afomera.dev/posts/2025-10-25-stop-giving-harm-a-microphone
And here's perhaps the weirdest thing about this Q&A update…it feels completely disconnected from the transfer of the repos to Ruby Core's ownership. Like, maybe you’d take out a couple of sentences, and if that transfer had never happened, this document could remain identical.
My guess? A lot of this was written before that transfer even happened. So that's why almost nothing here addresses the transfer. How does Ruby Core fit into the past month's events? Beats me!
It's really pretty clear to me at this point that there's no point in expecting current Ruby Central leadership to address the harms to date. At every turn they could have done something meaningful to get the train back on the track, and instead they engaged in more corporate-speak word salad that sounds like what non-technical people say whey they're trying to convert an email some hapless programmer sent them into legalese for a C-suite.
Time for new leadership.
“On the client tools side, while the repos could have been forked, as long as individuals could publish the gems from any source they want, no forked repository could have been the canonical and secure source of the tools.”
I have no idea what this word salad means. I really have no idea.
And this goes for a lot of the technical details. I don't understand what they're saying. Either I'm very stupid (it's possible), or they continue to obfuscate.
And here's perhaps the weirdest thing about this Q&A update…it feels completely disconnected from the transfer of the repos to Ruby Core's ownership. Like, maybe you’d take out a couple of sentences, and if that transfer had never happened, this document could remain identical.
My guess? A lot of this was written before that transfer even happened. So that's why almost nothing here addresses the transfer. How does Ruby Core fit into the past month's events? Beats me!
“The Board acted independently in their decision based on the internal timeline that was set; there was no sponsor-imposed funding deadline. Ruby Central maintains standard sponsorship agreements that do not grant operational control…sponsors were only briefed as part of normal communication and were not involved in any decisions or deadlines. ”
I don't believe this. I simply flat-out don't believe this. It flies in the face of all outside reporting to date.
“On the client tools side, while the repos could have been forked, as long as individuals could publish the gems from any source they want, no forked repository could have been the canonical and secure source of the tools.”
I have no idea what this word salad means. I really have no idea.
And this goes for a lot of the technical details. I don't understand what they're saying. Either I'm very stupid (it's possible), or they continue to obfuscate.
“Discussions about transferring the RubyGems and Bundler repositories under the Ruby Core team have been ongoing for several years.”
Oh really? This is the first I've heard of it. And believe me, I read just about every hot take and loose thread of debate in the past month across multiple Discords and social media. Nobody mentioned “the likely outcome here based on past conversations is Matz steps in and Ruby Core takes over”. That announcement felt out of the blue.
“The Board acted independently in their decision based on the internal timeline that was set; there was no sponsor-imposed funding deadline. Ruby Central maintains standard sponsorship agreements that do not grant operational control…sponsors were only briefed as part of normal communication and were not involved in any decisions or deadlines. ”
I don't believe this. I simply flat-out don't believe this. It flies in the face of all outside reporting to date.
Other than significant swaths of this text feeling machine-generated to me (or else it's the most bland corporate-speak on the planet), not much stands out here other than a handful of statements which are either factual (and all reporting to date is wrong) or bullshit.
I'll comment on a few of them below…
https://rubycentral.org/news/source-of-truth-update-friday-october-24-2025/
“Discussions about transferring the RubyGems and Bundler repositories under the Ruby Core team have been ongoing for several years.”
Oh really? This is the first I've heard of it. And believe me, I read just about every hot take and loose thread of debate in the past month across multiple Discords and social media. Nobody mentioned “the likely outcome here based on past conversations is Matz steps in and Ruby Core takes over”. That announcement felt out of the blue.
Other than significant swaths of this text feeling machine-generated to me (or else it's the most bland corporate-speak on the planet), not much stands out here other than a handful of statements which are either factual (and all reporting to date is wrong) or bullshit.
I'll comment on a few of them below…
https://rubycentral.org/news/source-of-truth-update-friday-october-24-2025/
 
      
  
             
      
  
             
      
  
             
      
  
             
      
  
             
      
  
            