-
Notifications
You must be signed in to change notification settings - Fork 201
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
Project seeking new maintainers #143
Comments
I'm considering taking over as a maintainer, but I will need access to someone who can serve as a "lifeline". As I mentioned in my post back in June, I have a vague understanding that there is a whole knowledge base required to maintain a gem properly, and I know I don't have it! Is there anyone available who can serve as that mentor? |
I'm interested - I'm using it in several of my personal projects, and although I've never really maintained a gem like this before I have a rough idea of what is required. Maybe @tovodeverett and I could pair up and do it together? |
As you can see by how long it took me to respond to the post from @starswan , I don't have a lot of spare time in my life right now, so I can't really commit to even helping. Also, I'd say I have less than a rough idea of what is required. I do have a number of monkey patches to yaml_db that I'd love to get into it, but for better or worse monkey patching has been the patch of least resistance for me. |
@jrgifford and I haven't been taking care of YamlDb in a while, so this project is officially seeking a new maintainer or maintainers to steward it into the future.
Do you use YamlDb and have an interest in taking over? Let us know here!
The text was updated successfully, but these errors were encountered: