php-resque
php-resque copied to clipboard
chrisboulton
Maybe this project needs new maintainer ?
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
+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.
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.
+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.
+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!
I think we can start with two or three group maintainer based on interest and previous contributions .... (just an idea)
Maybe this can be forked to the official resque namespace, and get maintained there.
CC: @tarcieri @steveklabnik @hone
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.
It needs a lot of work to be brought back up to date with the latest Ruby version, but there does seem to be plenty of interest in that area.
Hi all, it has been a number of months since this thread saw any activity. Is there any movement on reviving this project? It is such a shame to see it become stale like this.
This is definitely a great library... however no support made me switch to this https://github.com/josegonzalez/php-queuesadilla .. It works similarly to php-resque and great!
@steveklabnik: any news on this one? Can we at least get that fork and see how community responds?
@chrisboulton: any chance we get your ok on this one?
Sure thing, I'm happy to make a repo. Who should have access? this is the tricky question :)
Should we migrate my fork over? I've already merged the active PRs from here into its default branch; it wouldn't take more than a few minutes to switch everything to master instead, update the Composer config with the updated namespace, and have it ready to move..
Ping @steveklabnik @razvanphp @rajibahmed
As mentioned above, my fork is ready to go as a replacement repo already, if desired. It can already be used directly with Composer as is, but I'm more than willing to migrate it to the Resque namespace at any time.
@danhunsaker the question is will this project be maintained properly after being moved to Resque namespace. Looks like its a question of commitment and shared responsibility.
I may not have the knowledge and time required to maintain the repo but I surely can spend some times on it regularly if needed.
Yeah, it's a bit tricky to give any open source project the time it needs/deserves, especially when it doesn't necessarily directly impact paying work. For my part, I'm more than willing to put in as much time as I can spare to maintaining this project. I've made it a point to at least keep up with comments and discussions here, even when i don't have time for working on the actual code, so if nothing else, PR merging would probably be covered. But I'd still prefer a team of responsible parties, as proposed above, so that no one person can bottleneck the entire project (again).
Re-ping @steveklabnik @razvanphp @chrisboulton
Looks like at least two of us are willing to maintain the new repo...
Sorry all, have been ignoring email hardcore lately.
I have made a new empty repo at https://github.com/resque/php-resque and invited @danhunsaker and @rajibahmed . Please do with it what you will :smile:
Anyone else reading this thread, if you'd like commit as well, please let me know.
Let's see how this goes.
Hi,
Apologies - I can make all sorts of excuses as to why I haven't given this repository the attention it needs but at the end of the day - they're just excuses.
To this day, I am still heavily using php-resque in production. We're processing something on the magnitude of several million jobs/events a day using it.
Given how critical php-resque is to a lot of people, I believe a lot of scrutiny should be applied to almost all change sets. Not every proposed change should be merged just because they've implemented something with them.
If this project is moving to the Resque org, I'd ask that I'm included in that list of people that have access, and am involved in the decision/steering of this project going forward. There are a number of changes I'd still like to make to the project.
