-
Notifications
You must be signed in to change notification settings - Fork 182
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
Looking for new maintainer(s)? #535
Comments
Absolutely. There's a myriad of clients with no one actively maintaining them. The more help on this better, because I foresee a bunch of libraries being deprecated without someone with an interest in keeping it afloat. New features have been added into Riak, but not all of the clients, because it isn't in everyone's interest in doing so. This is something that should be discussed at the upcoming Riak user meetup, I think. I would rationalise the client libraries unless anyone is stepping forward to actively maintain it. |
This is good to know. I'm happy to help with this. When in the Riak users meeting? @martincox |
It's taking place next Thursday, in Manchester, England. Everyone is welcome, so if you are around that area, feel free to come along. |
There may be some remote arrangements for anyone who can't be there physically but still want to participate. |
If there is are any remote arrangements please let me know, or know where to check for them. I live in the states so unfortunately would not be able to make it. If remote arrangements aren't around (please don't go out of your way to get them for me, I may be busy during that time anyway), please pass on the message that I would love to help. |
This is a shame. |
I have been using this client in production for some time now, and have noticed that there seems to still be issues, releases, and more to be handled. I know that Basho is no more, so I was wondering if you are looking for anyone to help with maintaining the repo. I would gladly help with this project, please just let me know!
The text was updated successfully, but these errors were encountered: