Status of the project

[ono]

I notice that there are still many people using this library. I am very thankful to everyone and feel some responsibility to explain the status of the project.

I no longer use this library by myself. In fact, I haven't used Resque for long time. For day to day job, I mainly use Elixir. I have to admit that I'm quite behind the scene.

I would say that this library is maintenance status and here are some notes to clarify.

• I don't merge any pull requests for new feature
• I will merge pull requests which are relatively small changes for bug/security fixes e.g. #45, #46
• If Resque makes backward incompatible update, Resque-cleaner won't support the new version

You might ask for transferring the ownership but I am reluctant to do that in following reasons.

• The library was written long time ago and the codebase doesn't follow some good practices discussed recently. If you are motivated to maintain the library, you should rewrite the library and publish as a brand new gem
• It's MIT license. You are free to fork and publish as new gem as long as you publish it under the same permissions and add my name in copyright.

I hope you don't have a huge objection to the decision as Resque itself is not much active for years.

Thank you so much for your interest on this project. And thank you especially to all people who have contributed! 🏅

[josh-m-sharpe]

I just forked and pushed https://rubygems.org/gems/resque-cleanerer 0.5.0 including some PRs on this repo.