-
Notifications
You must be signed in to change notification settings - Fork 83
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
This gem needs to be maintained or the community needs a new fork that is maintained #55
Comments
🤔 @jnmandal are you open to adding maintainers? |
I’m open to adding maintainers. |
@joshuacronemeyer @schwern are either of you able to contribute some time to the gem? I have some time right now to invest, but would much appreciate assistance. |
Definitely open to having more maintainers. I've got very little time to contribute at the moment unfortunately |
I don't know how much time I can commit. I maintain another gem. @derrek if you wanted help reviewing a PR I could do that or triage a bug and bother reporters to create PRs for ones we think are important. I think it's OK to start small. Just showing a pulse in here would be good. |
@derrek I can help out. |
@johnnagro great! I'll get back to you tomorrow. |
@johnnagro can you please send me an email - see my GitHub profile |
Was this effort DOA? I don't mind. This is a great starting point. Thanks! |
I've been using this and there are bugs i'd like to fix. I also see a bunch of issues, PRs and forks with useful improvements. Are any of the original contributors @skippy @opti @derrek @schwern @amolk able to help? Or speak up? Maybe somebody with an active fork would be a good candidate as a maintainer? Give them commit rights and we can probably make a new release.
I think this gem could get better with a little love.
The text was updated successfully, but these errors were encountered: