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

[kabudu]

It has now been an additional month since the last update from @chrisboulton . Any movement on getting the 1.3 release?

[slince]

It seems to have been too long, is there a new version? @chrisboulton

[scaleupcto]

Isn't it just time to open up this repo to some people with a bit more time to make releases? Or has anyone organised a well-staffed fork?

[kabudu]

@robotrobot, @slince check out the fork from @danhunsaker . That's the one I switched to!

[slince]

@kabudu hi, it sounds greate! however how to install it from the packagist

[kabudu]

@slince here is a link to the packagist page:

https://packagist.org/packages/danhunsaker/php-resque

[rajibahmed]

As php resque is used by many ppl, we should change maintainer for this project https://github.com/resque/php-resque .... resque organisation has kindly opened its door to accept a stable php-resque ... as a community user. Think we should make all pull request toward https://github.com/resque/php-resque and move on. And we should have a in/formal process for reviewing and voting on a PR

[mkingbe]

@chrisboulton any news regarding this? Currently I do not have trust in this library considering the fact that has multiple issues and pull requests opened with no resolution, also is this debate of maintaining it from 2-3 years ago. Should I use this in production ?

[kabudu]

@mkingbe use this fork instead: https://packagist.org/packages/danhunsaker/php-resque

[bwegrzyn]

For those looking for PHP queue library with multiple adapters and that is actively maintained, this is a great alternative: https://github.com/php-enqueue/enqueue-dev

I'm currently using this in my projects and it's working beautifully with Redis.

[roynasser]

So almost 1 year has gone by, is there any consensus? I'm sad to see this go to dust :(

an eager community, many users, good product....and yet I think we will have to look elsewhere in order to keep up with php7, and some additional functionality that we want to add...

Is @danhunsaker 's repo being updated at all? (I see its abt 15+ commits ahead and 2 behind here? the 2 behind seems odd, but it may just be git confusion...) . Are we expecting to go into the official resque org? (IMO that makes most sense...)

@danhunsaker have you tested or know about compatibility of your fork with php7? we are starting our migration and php-resque is a big part of getting ready to upgrade...

[kabudu]

@RVN-BR I've moved on from php-resque and now use the library recommended by @bwegrzyn . It does look like php-resque is not moving any further forward. :/

[makasim]

It does look like php-resque is not moving any further forward. :/

I am a maintainer of enqueue library. It is quite matured and stable. @kabudu what kind of movement do you expxect (any issues or PRs) ?

[kabudu]

@kabudu what kind of movement do you expxect (any issues or PRs) ?

@makasim , my comment was related to the discussion history in this issue, such as the many open issues, the 1.3 release which hasn't happened yet, the version of the library in the resque namespace which hasn't seen any movement since it was created etc. I guess my comment was more of a conclusion that the library has been abandoned. I've found that the enqueue library has a more active development roadmap so I've opted to move on.

[makasim]

@kabudu let me know if something needs my attention on enqueue repo.

[pprkut]

I'm going to let the code stew in these environments for a little while, and then get a release out the door

@chrisboulton That was almost two years ago. Does that already qualify as "a little while"?

I realize cutting the release, moving to the resque organization and figuring out how the stewardship of the process should look like going forward is a difficult process. But 2 years? There's more and more forks with changes for their own requirements which are not getting consolidated back together. The longer this continues the more fragmented the community will get and the harder it will be to bring them all back together.

With all due respect to what you've done for the project in the past, I think it's time to make some decisions.

@danhunsaker, @rajibahmed Any input on how to get things rolling again?

[danhunsaker]

Out of respect for @chrisboulton, I'm planning to wait out the current month (October 2018), then move forward with the migration to https://github.com/resque/php-resque on my own if needed. I'm setting up reminder notifications to ensure I follow through as I write this. Look for movement to resume no later than 10 November.

[roynasser]

Waiting anxiously @danhunsaker

mjphaynes/php-resque seems to have activity already... Other forks also... maybe its best to fork from one of those? (Assuming others are still compatible? We are still running from this repo so it would be great if we can have a smooth transition)

[danhunsaker]

My plan is to use this repo, with mine (which contains many of the PRs originally submitted here) rebased atop it, as the starting point, and pull in other commits from other sources as they come to my attention. I'll be coordinating all this with the other maintainers, along with ensuring they're still on board.

[slince]

@danhunsaker looking forward to that

[makasim]

enqueue/redis would support message redelivery\recovery, delaying, expiration. So it might be a good replacement.

[kabudu]

@makasim would the redelivery be automatic? I use enqueue but still have an issue where messages sometimes do not get processed the first time round.

[makasim]

@kabudu Not sure what you mean by automatic. The message consumption was drastically improved in next major version (0.9).

[danhunsaker]

So my reminders never fired. I'm doing this migration work now.

[danhunsaker]

Just waiting to get access to the resque namespace on Packagist. Apparently somebody else registered their own package there years ago, and then has abandoned it since. :upside_down_face:

[danhunsaker]

And we're good! Feel free to migrate over to resque/php-resque now! I'm looking forward to some major improvements as PRs start being moved over to the new home, and merged in!

[Tamce]

I'm wondering whether this repo could be marked as Abandon.

I've never noticed that there is a resque/php-resque before I checked this issue.

[danhunsaker]

It should already be marked as abandoned when using Composer, but you would have had to install or update your dependencies sometime after 02 December 2018 to have Composer warn you about it.

[Tamce]

got it, thanks!