After 17 years dedicated to open source Ruby, @jodoshahas stepped down from the Hanami and dry-rb projects.
In Luca’s place, I will step up as Hanami project lead. I also remain a committed member of the dry-rb core team.
As for Hanami, we’re continuing on the path we’ve followed over the last few years. 2.1 is now out the door, and 2.2 is next. As we plan for this release, you can look forward to seeing updates right here on our forum.
I’d like to extend a heartfelt thank you to Luca for all his contributions to Hanami and Ruby. Collaborating with Luca has been a true pleasure for me, and I’m very proud of what we’ve been able to create together in Hanami 2. I’m looking forward to extending this vision for Ruby apps in the years to come!
If you have any questions about this transition, I’m happy to answer them here.
It’s great to see Hanami moving forward, and I love your work on it!
I was wondering what the plans are with the website, and especially the guides. Right now, I’m familiarising myself with v2 changes, and having the 1.3 guides intermingled is a bit confusing, especially for the less experienced devs on our team.
Are they eventually going to be two isolated sections?
I definitely want to revamp the site. Complete overhaul. Bring everything together under one roof: site, guides, gem docs, the works. Make a great new impression for people discovering Hanami, and make everything easier for our small team to maintain.
This will take a bit of time to happen. I’d like something to get started in the second half of this year, but I would be unsurprised if it took until early 2025 to ship it. It all depends on how much volunteer effort we can drum up.
In the meantime, could you please share a little more about what’s confusing with the current guides? To my knowledge, the 1.x and 2.x sections should be completely separate, governed by the version selector at the top of the page. Are you seeing intermingling?
I do think there might be a bug with the search where it doesn’t show results within the current version only. I’ll see if we can get that fixed up before the release of 2.2 (i.e. in the next month or two).
