-
Notifications
You must be signed in to change notification settings - Fork 159
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
Maintainers wanted! #84
Comments
I'd be willing to help out. Hopefully others are interested in contributing too since I can't dedicate too much time. |
I don't know if the repo has been taken up for further maintenance yet. |
I can dedicate some time too. |
I will help |
i will help too |
1 similar comment
i will help too |
TL;DR
Let me know if you'd like to take over as one of the maintainers of this library. If no one wants the responsibility then the repo and library will be marked as
Deprecated
.Help Wanted
I haven't had the time or inclination to maintain, update or improve this library in quite a long time. @starkej2 has been an invaluable help to me, as he has taken over most of the work looking at issues and cleaning things up. I consider it to be feature complete for what was my own use, but there are quite a few requests for fixes, features and improvements which I'll probably never implement.
This is something I've been thinking about (and postponing) for quite a while. I would like for users of the library to either know that it's being maintained or be warned that they are on their own when using this code. These two options translate into either finding people who are interested in taking over this repo or deprecating this library.
If you'd like to take over then please let me know. I can create an organization and move the repo over. We could also switch to using jitpack instead of the existing maven repo, which would give quite a bit of flexibility. I would still check how things are going every once in a blue moon and, who knows, might even contribute to it again!
If no one wants to take over then I'll mark the library as deprecated. The code and existing artifacts will remain in their respective places and everything should work until it doesn't (incompatible support libraries, API changes, etc).
Thanks,
Eduardo
The text was updated successfully, but these errors were encountered: