Maintenance of resque-pool

[spajus]

@nevans, it seems like resque-pool has plenty of pull requests and issues that are ignored for quite a long time. Would you like to give somebody rights to maintain the repository and release gem updates? I'm using resque-pool heavily, so I would be willing to help maintain it. Possibly somebody else would too.

[wollkind]

As someone with a couple of open issues that haven't even been commented on yet, I'm all in favor of this. I probably don't have a lot of time to help maintain, but I'm happy keep reporting on issues and give my best guess for fixing them as they come up in my work if it looks like they'll get addressed.

[raphaelcm]

+1

resque-pool as it currently stands is a great start, but could really use some TLC.

[oesgalha]

+1

[spajus]

I've tried to email @nevans to no avail. I'm thinking of starting a fork and maintaining resque-pool over there.

[raphaelcm]

@spajus go for it. would love to see this project actively maintained. thanks for spearheading this!

[spajus]

Forked it to Vinted organization: https://github.com/vinted/resque-pool
Will start applying old PRs and preparing new gem some time soon. I hopefully won't be alone maintaining it there.

[nevans]

Tomas (et al), sorry I've been so neglectful. If we discuss (and document in README.md or CONTRIBUTERS.md) commit, merge, and release policy, then I will be comfortable giving commit rights to this repo (or pointing folks to an organization's repo, e.g. vinted) and rubygems co-ownership.

My $0.02:

1. We should commit to semantic versioning.
2. We should be conservative with releases, which simply means that:
   • tests pass
   • a new release shouldn't be cut until one or more of the maintainers has been running the latest RC in production for a week with no critical bugs.

What do you think?

(As another point of interest, there is also a new project https://github.com/spraints/resqued that does much of what resque-pool does, but with slightly newer cleaner codebase. Only one committer so far, and github doesn't seem to have advertised it much, but I think they are using it in production.)

[spajus]

@nevans, thanks for response 🙇, I'm relieved that we won't have to live with that fork.
Your suggestions sound good. Might need little more details on how to deal with PRs. Will submit a proposal for CONTRIBUTING.md some time later this week, unless someone else does it first.

As of resqued, may be a nice project, but resque-pool is battle tested, and migrating our job farms to something else that has considerably smaller community would be risky and challenging.

[darkness51]

@nevans @spajus something new about new version?

[spajus]

@darkness51 I got bogged down with other things and didn't find the time to prepare a proposal for CONTRIBUTING.md, so everything got covered in dust in here. It would be nice to continue this though. Perhaps somebody else would like to help?

[spajus]

👍 @zmillman for stepping in

[nevans]

We have a first pass CONTRIBUTING.md, but we still don't have anyone other than me pushing gems. I don't think this ticket should be closed until I have either proven myself to not be a negligent maintainer or have given several other folks gem push rights. :)

[spajus]

Yep, good point... :)

[nevans]

FYI: since lots of folks have been using 0.4.0.rc2 (or a fork based on that) for over a year, clearly it was just time to SHIP IT! So I did. 0.4.0.rc2 was promoted to 0.4.0.

I also pushed 0.5.0.rc1 (which is based on 0.4.0.rc3 plus a bugfix for resque-multi-jobs-fork). If you want to help me with maintaining resque-pool, please try it out now. 😄

[nevans]

If you want to help with maintenance, here's another thing you can do: check out #120 and provide input there. Specifically, I want to analyze the long-lived branches to see which ones need support before semver 1.0.0, so we can support them without releasing 2.0.0.

[nevans]

Please test out the 0.6.0-rc1; big new custom config loader feature.

[michaelglass]

@nevans any progress here?