-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contributors #78
Comments
Hey @erkie, Glad to hear your team is using go-workers! I welcome collaborators, if you have any ideas for where you'd like to see the project go, I'm all ears and happy to help! We use this project extensively in production for many of our services as well. Any issues/improvements we find are pushed here. The staleness is mainly due to it being really stable for us, allowing us to focus on other things. |
I see that customer.io seems to be using their own fork https://github.com/customerio/go-workers which is ahead of this repo, but doesn't have issues open. Do you intend to continue maintaining this repo here? If yes, it might make sense to pick some of the additions of the customerio fork, e. g. Gomodules (#99). If you don't maintain it, how about
BTW, no bad feelings. I am not using this code (but looking for something like it). Glad you put it our here. Just trying to make it easier for the community to judge whether it's worth investing into this project. |
We have since switched to https://github.com/digitalocean/go-workers2 which works great, but has some breaking changes. |
@jrallison you've done an amazing job with this project. We rely on it a lot for our infrastructure and it works amazingly. We do around 20,000 jobs per minute on very commodity hardware which is so cool.
Looking at this project it seems a bit stale, the most recent merged PR's and commits are from 2016. Would you be willing to add some collaborators so we can kick some life into this project?
The text was updated successfully, but these errors were encountered: