Replies: 2 comments 10 replies
-
|
Beta Was this translation helpful? Give feedback.
7 replies
-
I agree that I haven't had a lot of time with my current role to keep rate-limit-redis maintained. I'm happy to have it join y'alls organization and have CI be enabled for publishing to the npm repository from it. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @wyattjoh, @linyows, @2do2go, and @JGLTechnologies!
Firs of all, thank you for creating rate-limit-redis, rate-limit-memcached, rate-limit-mongo, and precise-memory-rate-limit respectively.
I had an idea that I wanted to propose: would you like to transfer your stores to the express-rate-limit org and have @gamemaker1 and I share in the support and maintenance of them?
It occurred to me that it might feel like I was trying to take something away from you, which is not the goal. So if you'd prefer, we'd also be happy to help by contributing to the repos in their current locations, via PRs, code reviews, etc.
(For context, we've been slowly making some improvements to express-rate-limit to address longstanding issues, warn about common misconfigurations, and generally help users "fall into the pit of success", and I think some of these could be extended to the stores also.)
This is an individual decision for each of you, but I thought it might be good to start a discussion here with everyone and see where it takes us.
All the best!
-Nathan
Beta Was this translation helpful? Give feedback.
All reactions