Is this project dead?

[bkuhlmann]

Hello. 👋 I noticed this project hasn't been updated since 2024 (nearly a year ago) and wanted to check and see if any active development is being done on this? I'm making use of this project but worried is this is also at risk. Thanks. 🙇

[adam12]

Not dead. But not necessarily under active development either.

[jrochkind]

I guess one question for maintainers is if there would or could be enough capacity/interest to review the work you are thinking of for hanami in PRs here, as opposed to you doing the same work in a fork.

[bkuhlmann]

Adam: Correct, for the most part. There is external support via Paweł Świątkowski's Hanami Shrine but it's quite old now and doesn't support 2.x.x. Also Shrine does have Model and Sequel plugins but they don't work with Hanami 2.x.x. out of the box. To be clear, I'm not asking for Hanami support in Shrine. That can remain external but I would think low-level support for making Hanami support easier would be good to have.

Janko: Thanks. Yeah, Hanami needs Rack 3.0.0 support as well which hasn't seen much traction either. Given that you have no plan for further development, how will any changes to Ruby be dealt with, quality of life improvements, bugs, etc. be addressed in a quick manner?

Jonathan: My litmus test, so to speak, is to always submit an issue and see if it can be resolved quickly. If a simple issue like that can't be addressed (which is currently flooding my console) then I get worried. 😅

[janko]

@bkuhlmann I saw your issue, and remember thinking I wished it was a PR that I can just merge 😉 That would make it really easy for me 🙂

[jrochkind]

Makes sense, but a simple PR may be a better test than a simple issue, if we're testing for if PRs can get merged! it can be of course much quicker to merge a PR than to create one in response to someone else's issue! And feedback from maintainers on their intention and understanding of current capacity never hurts!

[bkuhlmann]

Janko: I've submitted a fix. If this gets applied, can a patch be released as well?

Jonathan: It's expensive to submit a code review on a project you've never contributed to before which is why I always start with an issue first (less ceremony and a good check to see if the lights are on). The problem with straight up code submissions is that you have to fork the project, set it up, get the test suite running, etc. which is a lot of work for a project that might be abandoned. I also don't like to keep forks around longer than I have to (this is akin to long running feature branches -- always a maintenance burden).