THIS PROJECT IS LOOKING FOR A NEW OWNER

[bradvogel]

Hey everyone!

The Mixmax Engineering team can no longer maintain this repo. We're moving away from Bee Queue over to SQS.

We're looking for a new owner of this repo.

You:

• are an experienced engineer working on a team that's using Bee Queue at scale.
• have extra time to be able to review and merge PRs.
• have an exceptional attention to quality. Many people and organizations rely on this project! Let's keep it stable.

If you're approved, we will:

• give you write access to this repo in order to merge PRs (all PRs must be reviewed by other maintainer, per our rules)
• be available if you have any technical questions
• after some time and trust is built up, we'll make you a project admin

[compwright]

I'm an experienced engineer using bee-queue in production. I'm not sure what qualifies as "at scale." I meet the other criteria and have a number of open source packages that I maintain.

[bradvogel]

@compwright Thanks!

Are there PRs in here that you feel are ready to merge? Please comment in them. I'll double check the code, then give you write access if we align.

[compwright]

@bradvogel yes, for starters all the dependabot PRs should be given priority.

There are a handful of two others, and I will tag you in a comment in them.

[bradvogel]

I gave you write access to this repo, @compwright. I see that you maintain other repos, so trust you to take good care of this one.

[compwright]

@tmeasday you interested in helping out as a maintainer?

[tmeasday]

Hi @compwright we (at Chromatic) are looking to migrate away from bee-queue in the next year, so long term I guess not, but in the short term we can probably help out. cc @codykaup

[compwright]

@bradvogel asked if I knew of anyone that could join the maintainers team, and you came to mind. Right now it's just me. Best for the project if there are long term maintainers besides me. But I'd take short term help while I get acclimated.

[tmeasday]

For sure, ping me when you need. I'm more familiar just as a consumer, the only code I wrote was 3 years ago and even at that stage I found the test strategy pretty hard to understand, but I get the basic code flow in the package.

[jorenvandeweyer]

We use bee queue in production ~400 jobs/s. I'm willing to review PR's.

[compwright]

Thank you @jorenvandeweyer! I will tag you on upcoming PRs to review.

[entrptaher]

I made a short experiment based on bee-queue with a better worker_threads this evening only to find this issue :D

https://github.com/entrptaher/extended-bee-queue

[dogabudak]

I am using bee-queue as well. I am willing to contribute.

[bradvogel]

@dogabudak thanks! Please send PRs our way and we'll review. Once trust is earned, we'll make you a maintainer.

[Rohithzr]

Is there someone working on the ioredis implementation or is that abandoned? if it's still something people want, I can work on adding that capability. If this is not something the community is looking for, then I will switch to a standalone Redis cluster for now.