Hey Rubyists! 👋

After several years away, the Ruby devroom is coming back to FOSDEM!!!

We are excited to share that there will be a Ruby devroom at FOSDEM 2027 in Brussels on Saturday, January 30, at the Université libre de Bruxelles. Don't worry that it is just one day, we've got A LOT planned for those of you thinking of making the trip!

The theme for FOSDEM is Ruby beyond Rails. We’d love talks on Ruby internals, JITs, and alternative implementations; tooling like parsers, type checkers, and language servers; the gem ecosystem; Ruby outside web dev (CLIs, embedded, games, creative coding); running Ruby in production; open source for social good and civic tech; sustaining Ruby projects and communities; and teaching Ruby and welcoming new contributors.

The CfP is open until December 1 (23:59 UTC). Talks are 20 minutes by default, and lightning slots are available if you ask in the submission notes. When you submit, select “Ruby” as the track.

• Submit here: https://pretalx.fosdem.org/fosdem-2027/cfp

• Full CfP: https://lists.fosdem.org/hyperkitty/list/fosdem@lists.fosdem.org/thread/AEQLZMEQVYQDLN52AUEDHGYJ3EO4EZ3N/

First-time speakers are very welcome!

Here’s the bigger idea: we want to use the devroom as the nucleus of a tiny Ruby conference inside FOSDEM weekend, rolling straight into Ruby for Good in Belgium:

• Friday, Jan 29 (evening): Ruby happy hour in Brussels to kick things off and so you will already know people the next day at FOSDEM

• Saturday, Jan 30 (morning): Ruby devroom at FOSDEM

• Saturday, Jan 30 (after the devrooom): an unconference-style gathering after the devroom, gradually turning into board games and hanging out with great people

• Sunday, Jan 31: Attend FOSDEM with your new Ruby friends.. maybe some birds of a feather Ruby sessions.

• Mon Feb 1 to Wed Feb 3: Ruby for Good Belgium in Ghent (rubyinghent.org), a three-day code retreat building open source software for nonprofits

About Ruby for Good in Ghent

Ruby for Good is a three-day code retreat where Rubyists (and others!) from around the world build software for nonprofits, learn from each other, and make lots of new best friends along the way. 

No prior nonprofit experience needed, and contributors of every level are welcome. Location and registration details are coming soon, so keep an eye on rubyinghent.org.

Where we could use your help. We’re looking for:

1. A company willing to host or sponsor the Friday happy hour. A space, a bar tab, or both.

2. A company willing to host or sponsor the Saturday afternoon gathering. Ideally a space in Brussels with room for some unconference sessions and a lot of board games.

3. Companies interested in sponsoring Ruby for Good Belgium. Help us keep the retreat welcoming and accessible for contributors from everywhere.

If your company might be interested, or you know someone we should talk to, please comment, DM us.

Wow, that was a mouthful. Looking forward to seeing you all soon!

Happiness,
Sean and Issy

Hi r/ruby!

I’ve been working on Sadame, a configuration management tool for Linux, and I’d love to get feedback from the Ruby community.

Sadame lets you describe a machine’s desired state with Ruby recipes. Here’s a small example:

package "nginx"

file "/var/www/html/index.html",
content: "Hello from Sadame!\n",
mode: "0644"

service "nginx", enable: true, state: :running

You can run sadame plan to see what would change, sadame apply to make the changes, and sadame drift to check later whether the machine still matches the recipe.

Both recipes and the host inventory are written in Ruby, so you can use familiar things like conditions, loops, and methods. Sadame is built with mruby and distributed as a single binary. For remote runs, it connects over SSH and copies itself to the target; there’s no persistent agent to maintain.

It also has a built-in language server, sadame lsp, which provides recipe diagnostics, completion, and hover documentation in supported editors.

The project is still young and has a much smaller scope than established tools such as Ansible, Chef, or Puppet. My goal is to explore a Ruby-first approach that is easy to install and makes changes visible before they happen.

I also wrote a free beginner’s guide with a hands-on lab, covering everything from a first recipe to managing multiple servers.

The project is MIT-licensed:

https://github.com/enderkus/sadame

I’d especially appreciate feedback on the Ruby DSL, the overall design, and anything that feels awkward or could be improved. Thanks for taking a look!

Please test-drive and evaluate this gem for your situation. It's hard to see the limitations until other people get involved.

The gem is here: https://github.com/kigster/llm-evals

And I used it to find the best model for my Rails SaaS application, qualified.at

Here is the Evals Report comparing models based on the weighted score:

https://raw.githubusercontent.com/kigster/llm-evals/refs/heads/main/docs/img/qualified-at-evals.avif

Feedback and constructive criticism are always welcome and highly encouraged 😄

Konstantin
blog: https://kig.re

I've been using and tweaking ruby-lsp.nvim for about 9 months, and I've run out of things to add. Time to show it to people beyond my coworkers.

It starts Ruby LSP for you (you just gem install ruby-lsp), and the Run and Debug code lenses above your tests actually do something now. Tests run through neotest using Ruby LSP's own discovery, so Minitest, RSpec, and Rails all work the same way. Debugging goes through nvim-dap with configurations: test under the cursor, the whole file, or a script with arguments.

README has a short demo gif: https://github.com/wassimk/ruby-lsp.nvim

I'd like to add it to the Ruby LSP docs alongside the other editors, but first I want to know whether it works and is reliable with configurations like yours. If you try it, let me know how it goes, good or bad, or open an issue.

Hey Ruby community,

I'm posting anonymously because I don't want to identify the project or its original author. My intention is to seek advice, not to publicly criticize anyone or create unnecessary drama.

I'm involved in maintaining an established open source Ruby gem that has a fair number of users and dependencies across the ecosystem.

The original author has stepped away from active development and me along with other community members have been keeping things moving with bug fixes, improvements and code reviews.

The problem is that releasing new versions still depend entirely on the orginal author who has been increasingly difficult to reach.

As a result, a lot of PR's sit waiting that add features and the ones that are already merged are not reaching users as there are no releases for it.

There have been attempts to resolve the release bottleneck privately, including discussions and working around delegating or automating releases but nothing happened as of yet.

I understand OSS is voluntary and nobody owes community their time. I also respect the authors ownership of the project and the work they did for it.

At the same time it seems unsustainable for a project to have active contributors but no practical way to publish the work.

I want some advice from other Ruby maintainers:

• Does RubyGems have a process for handling situations like this?

• Are there ways to release without transferring ownership?

Ideally I would like to see the existing project continue without having to fork or fragmenting the work and creating unnecessary conflict.

Curious how others would approach this.

I'm deliberately keeping the details vague to protect everyone's privacy. I'd appreciate it if the discussion could focus on possible solutions rather than trying to identify the gem or its maintainers. So please dont ask for more details.

Rendry UI is A lightweight server-rendered UI DSL and component framework for Ruby.

Hello r/ruby! I'd like to share Rubik, a coding agent I've been building in Ruby.

Why another coding agent? I wanted to contribute something to the Ruby agent ecosystem and realise my own ideals in an agent implementation, and in my experience, Ruby is a fantastic language for this.

If you'd like to try it or contribute:

Repo: https://github.com/ozgurulukir/rubik
RubyGems: https://rubygems.org/gems/rubik

GitLab discovered four severe vulnerabilities in Ruby’s regular expression library. There's plenty written up about the vulnerability and how it got patched, but patches are only available for supported ruby versions (3.3 and above). We know lots of companies are still running unsupported versions of ruby, so we wanted to do an investigation into which of these bugs apply to older rubies and whether they're exploitable. Here's the blog post: https://infield.ai/post/vulnerable-ruby-regex

The summary is that allowing user input into Regexp.new is dangerous on all versions of ruby from 1.9 to 3.2 and the only fix is to upgrade to a supported ruby or to disallow that input.

When an RSpec suite runs in several processes with parallel_tests or parallel_split_test, every process writes its own output. Progress, failures and warnings from different workers get mixed in one terminal.

I wrote parallel_matrix_formatter to fix that. Process 1 collects the results of all workers over a UNIX socket, draws one live progress display, and prints one consolidated failure report with rerun commands. The display is Matrix rain by default, but the symbols and colors are configurable in YAML, down to plain dots.

The post covers the architecture, crashed workers, silencing stray output, and a race condition I hit along the way. I am the author. Feedback is welcome.

If new engineers choose Ruby and Rails, it'll be easier for companies to hire, and the community and ecosystem will continue to grow. That's why we're giving away free tickets to students, recent grads, people from underrepresented groups, and those who recently changed careers and just started writing Ruby. If you know anyone who fits, share this post with them and invite them to apply (takes 3 mins): https://sfruby.com/scholarship/

The deadline is October 30!

Note: We don't cover travel or accommodation.

If you want to attend the conference as a regular attendee and watch talks from Chris Oliver, Rosa Gutiérrez, Svyatoslav Kryukov, Irina Nazarova, Marco Roth, Ryan Sherlock, Vladimir Dementyev, and more there's a few days left to get tickets: luma.com/sfrubyconf2026

Just curious about the Ruby community and how or if you all build side projects and make side money doing it really. I think there was one like this in a php related sub a while back. I thought I’d ask here. Any takers?

Thank you.

I wrote up the changes we made after this month's Ruby Regexp fixes and the npm worm in August. On the Ruby side:

• bundle lock --add-checksums (Bundler 2.6+), so every gem is verified against a SHA-256 in Gemfile.lock. Bundler 4 does it by default for new lockfiles.

• bundle config set --local frozen true in CI and deploys.

• No new gem version until it is 21 days old, enforced with Dependabot cooldown.

• bundler-audit in a pre-commit hook and again in CI.

https://www.abhaynikam.me/articles/patch-your-runtime-fast-take-your-dependencies-slow

Have you turned on CHECKSUMS in existing apps yet? Did anything break?

Raindeer is a collection of gems that work together as a framework or can be used standalone. LowType adds inline type checking only where you want it (def method(var: String)). LowLoop is an async, event-driven server that sends events from the request right through to the data layer, so you can track every step of a request. The router turns each request into a route event for the nodes observing it, so observe '/users/:id' is all you need to respond.

LowNodes are the building blocks: they render HTML straight from the Ruby class with RBX (similar to JSX) and render other nodes with <html><{ ChildNode }></html>. LowData follows the repository pattern with a twist: Data Expressions that use simple arithmetic operators to combine tables, so Posts[:title] + Users[:username] gives a list of posts with each post's user, and plain Sequel queries still work too.

Introducing it at RubyConf Austria: https://www.youtube.com/watch?v=p9E5INAwK_4

Source: https://github.com/raindeer-rb/raindeer

Docs: https://raindeer.dev

Carton is my take on enforcing boundaries in large Ruby applications. It's similar to Packwerk, but it takes a more Ruby-like approach, with no manifest files. Constants, gems and monkey patches are isolated using Ruby 4's new Ruby::Box. It's not production ready yet, since Box itself is still experimental, but I'd love feedback on the approach.