Maybe this project needs new maintainer ?

[rajibahmed]

Hi Chris,

I have been using this project in production from 2012. It solved many of our problems. And its a great idea to keep the whole redis compatibility. So, we can use tools already created for ruby.

Unfortunately, the progress and bug fixes are really slow, last two year. I want to propose that you can create a php-resque organization where there are more then one owner or add other developer as maintainer to this project.

This is a useful project, but still it needs to move forward in my opinion.

//Best

[danhunsaker]

+1

[BenoitDD-URIOS]

+1

[scaleupcto]

+1 I'm afraid. We love the library too, but will probably be forced to find something else if we cannot resolve some issues we have. We would be happy to help fix some critical bugs for it.

[bburim]

I think all of us ever did some changes to the original library to fix some bugs which brought us problems. It would be good to join all the efforts and to have one stable repository with all fixes together in one place.

[rajibahmed]

+1 @bburim

[lucups]

+1

[rolfvreijdenberger]

+1. great library and work, thanks for that.
But when moving forward while trying to use the library directly, we cannot work with the velocity for which changes are implemented. we have to resort to using our own fork.

[nataliaAznar]

+1

[fyfey]

+1
PHP definitely needs this, and php-resque is the best solution out there IMHO. I hope someone takes it on soon as this could be even better - and people are clearly happy to contribute by the amount of open pull requests!

[amiri27]

+1
But do we have volunteer for that?

[rajibahmed]

I think we can start with two or three group maintainer based on interest and previous contributions .... (just an idea)

[azngeek]

+1

[HMAZonderland]

Lets fork the project and start there with maintainers.

[razvanphp]

Maybe this can be forked to the official resque namespace, and get maintained there.

CC: @tarcieri @steveklabnik @hone

[steveklabnik]

I would not be totally opposed to giving a port of Resque a repo under the Resque organization. I'm a little uncomfortable starting a fork there, exactly, but it does seem like Chris has checked out. Happens to the best of us; I wasn't exactly a great maintainer of Resque myself.

It seems like he's active on Twitter though; posting a few days ago. Maybe he'll respond there, I'll try tweeting at him.