Really happy @hanamirb.org 2.3 is out with some improvements I helped work on! including a `hanami run` command + resources routing DSL. Always room for more in the tent, try it out and contribute back to help make things better though! hanamirb.org/blog/2025/11... #ruby

This is our first release of a new era — courtesy of our patrons and their financial support. Thank you @mike.contribsys.com, @baweaver.bsky.social, @honeybadger.io, @fastruby.io, & @appsignal.com! Hanami 2.3 couldn’t have happened without you. We’d love for you to join them. sponsor.hanamirb.org

Hanami 2.3 is out! This is a fantastic release, with improvements all across the stack, but the thing I’m most proud of is the whopping THIRTY TWO Rubyists who’ve chosen to contribute and make Hanami better. Thank you everyone! 🥰

🌸 Hanami 2.3 is here, and it’s racked and ready! This is our biggest release yet. Rack 3, resource routes, and so much more. hanamirb.org/blog/2025/11...

Here's what I've been up to these last few weeks: noteflakes.com/articles/202...

Weeknotes, Releasemas Eve edition. Dry Logger improvements, final code changes, a whole lotta docs, and an explanation of why my timing estimates need slack. timriley.info/posts/contin...

where my rubyists (old people) at??

Also today: entering the home stretch before Hanami 2.3. All the code is done. Just guide updates, upgrade notes, and the announcement post, and we’ll be ready to go. Probably not next week (I still need to sleep). But *definitely* the week after.

I substantially improved the docs for Dry Logger today. This is the logger you get in Hanami apps, but you can also use it anywhere you like! It’s a pretty nice logger. Check it out! dry-rb.org/gems/dry-log...

Weeknotes: resourceful routes, another batch of contributions (including a new bin/setup, plus a little something just for our friends at gem.coop), speaking at open summit, and a cool new open source Hanami app! timriley.info/posts/contin...

You know… Ruby Central’s takeover of rubygems GitHub org ONLY worked because it could be executed within seconds, and by doing so, prevent the possibility of revert. If the ownership change was a PR it would never have been approved. If RC is “right”, why did they need the atomic switch?

thoughtbot’s Open Summit has started and I’ll be speaking on Hanami in 20 minutes! Here’s the link if you just want to drop in: us02web.zoom.us/j/87946598627

Continuations: more work getting Hanami 2.3 into shape, a year of Dry Operation, resourceful routes getting close, and finding the positives in a grant rejection. timriley.info/posts/contin...

I wrote my most personal blog post to date. It summarizes some of my personal feelings and experiences in the Ruby/Rails community. afomera.dev/posts/2025-1...

the former maintainers of Bundler and RubyGems have a proposal: we want to move Ruby forward andre.arko.net/2025/10/26/w...

Let's move Ruby forward. martinemde.com/2025/10/25/m...

Martin is experienced, insightful and inspiring. Someone should find a way for him to work on Ruby’s package management toolchain!

One takeaway is that the open source world is an amazing place! It's marvelous how well this usually works. This is distributed trust at scale via education and support (rather than control). All the work to help people learn security and provide best practices mostly seems to work. Wonderful!

Companies should scan their open source. Full adoption of trusted publishing could have foiled NPM’s Shai Halud. Fighting about shared ownership models is horribly destructive when it makes the people leave that understand these problems. That’s the real security vulnerability.

If all you need to make your supply chain secure is CLAs for devs and a non-profit administrative staff holding keys to the world, remember that most package managers still run untrusted code on install, packages go live with minimal scanning, and best practice publishing security adoption is low.

You might wonder, “how can a group of friends be sufficient for global enterprise software supply chain security?” The answer for me is that these people were there BECAUSE it was so important. RubyGems.org has had no major outage in 14 years. This is not a fluke.

The team that managed rubygems was formed by building social connections with people that cared enough to work on rubygems in their free time. It is at its core a trust based team of equals. This is why corporate takeovers that take advantage of that trust hurt so much. Trust is all we had.

We spun up this feature petition with GitHub that I think would genuinely help a lot of projects and companies, open source or not. github.com/orgs/communi...

I wrote a couple of articles juxtaposing my experiences as a Ruby developer with my life as a Ukrainian surviving the war (still trying to find insights for development practices in it). Got a fair bunch of "why politics again :roll-eye-emoji:" comments (not all of them, thankfully).

"The better Ruby Discord. Ruby is about developer joy, not divisive political views. The sooner we purge politics from FOSS the better." Saw this quote tweet today, For some of us, our lives and ability to exist _are_ those divisive political views mentioned.

I've just released Papercraft 3.0: a new rendering API, improved support for XML templates and more. noteflakes.com/articles/202... #ruby #papercraft

Weeknotes: flexible formats, more improvements, some house keeping, another beta, a new maintainer, Ruby Retreat goings-on, and a surprise conference appearance! timriley.info/posts/contin...

My @xoruby.com talk today will be free for anyone to join! Thank you to @jremsikjr.bsky.social and XO Ruby for making this happen!

We're inviting you to join us for a talk from @timriley.info on @hanamirb.org later today. 4:15 PM – 5:00 PM (Pacific Time) Details available here: www.xoruby.com/event/san-di...

“Ruby is the essential official language for Rails and the Rails ecosystem. To provide the community with long-term stability...”

Pretty chuffed I get to tick “Present at @xoruby.com” off my bucket list! See you all across the internets—tomorrow!

What I talk about when I talk about Ruby – @timriley.info [Presented remote from Australia]

XO Ruby San Diego now with 100% more @hanamirb.org Details soon.

So this was nothing to do with operator agreements. The original RubyGems maintainer team would have been the right group to decide upon and figure out this transition.

Ruby Core accepts stolen RubyGems projects that their own insider HSBT stole from the maintainers through Ruby Central. www.ruby-lang.org/en/news/2025...

“Another beta!” you exclaim. “And so soon! How did you do it?” With the support of @mike.contribsys.com, @baweaver.bsky.social, @honeybadger.io, @fastruby.io, and @appsignal.com, that’s how! These are our patrons, and we think you can become one too: sponsor.hanamirb.org

Hanami 2.3 beta2 is out! Here we introduce a `hanami run` command, improve action formats config, bump our minimum Ruby, and bring a range of other fixes and improvements. This will be our last beta for this cycle, and we’d love your help with testing! hanamirb.org/blog/2025/10...

#hanami for #rails developers is a 4-part series showing how to learn Hanami: ryanbigg.com/2025/10/hana...

Don't miss Karl Oscar Weber's talk, "How to Fail." How to do it, avoid it, & what to do when you do fail. Failure isn’t the end. Oct. 10/18, Found Studio – 5490 La Jolla Boulevard, La Jolla, CA 92037 🎟️ Grab your ticket for $100: xoruby.com/event/san-diego/

I appreciate the nuance in Robby’s take and if Ruby Central was acting in good faith, I want to see them work to make it right with the maintainers. Actions speak louder than words.

4. It hasn’t explained to the community what kind of pressure it was under to perform this takeover or who were pressuring them. 5. It hasn’t rescheduled the Q&A that was promised to the community. 6. It has refused to come to the table and negotiate with the maintainers and/or community members.

As of right now: 1. Ruby Central is *still* in possession of the GitHub organisation and gems that it stole. 2. It hasn’t published any kind of justification for this. 3. It has threatened an ex employee for responsibly disclosing that it left him with root access to live production systems.

Nothing says “summer is coming” quite like your first few mangoes of the season 🥰

My last week in Hanami: timriley.info/posts/contin...

Wanna contribute to open-source? This is a good chance to contribute to @hanamirb.org and get your feet wet! github.com/hanami/cli/i...

a couple days ago the way Hanami, Dry and Rom all work together clicked for my little ruby brain. took a while to get there but it’s really exciting! easy to compose them on their own too, but together it’s a treat to work with.

sheesh Hanami is fast! I haven't needed my tricks to make things feel even faster yet!

Starting a new series called: #HanamiTips You can implement your own logging behavior for @hanamirb.org by overriding the config.logger.logger_constructor in your app.rb file. This one records the logs to stdout AND a log file and rotates logs daily or at 1mb in size.

~20 years of Ruby/Rails experience ~5 years of engineering management ~15 years public speaking at confs …a lifetime as an artist and designer I'd be great as: -StaffEng -Senior EM / Director -VPE (at small/medium size company) shanebecker.dev