Ideas for sustainable maintability?

[junaruga]

vegas's last commit is in January, 2012. No update for 8 years.
For a open source project, it's natural.

However resque (GitHub) is using vegas as a runtime dependency, I want to see vegas is maintained sustainably by people using it, as Ruby releases the new version once per a year.

Adding CI is the one step. I sent the PR in the past.

Finding new maintainers is an another way.
For example, in case of rack-test that has a challenge of maintainer's resource, it sees rack-test project repository will be moved to rack organization. See rack/rack-test#256 .

So, if vegas project has a challenge of maintainer's resource. After the communication with resque project's maintainers, moving the vegas project to the resque organization is one of the way to improve it.

What do you think?
Do you have comments?

[junaruga]

https://rubygems.org/gems/vegas
The concern is
vegas depends on old version of the gems or outdated gem.
It considering rack 1.X, but does it work with the latest rack 2.X?
It depends on sinatra 0.9.X, but does it work the latest sinatra 2.X?
It depends on bacon that is a kind of lightweight RSpec. But the bacon stopped the development already. We can migrate it to RSpec.

I am observing an error on the relatively new version of the depending gems.