-
Notifications
You must be signed in to change notification settings - Fork 38
Active Maintainer? #74
Comments
@ryanhefner thanks for the message, and sorry it took so long to get back to you! I'd love some help maintaining - I unfortunately don't have the time to devote to seeing though PRs and responding to issues. If you're still interested, I can go ahead and make you a Maintainer in the repo settings. I'll likely continue to handle publishing new versions of npm myself for the time being, but after establishing trust, I can hand off the keys to you, or we can look at something like semantic-release to automate all that! |
Hey, @nwalters512, sounds good. Yeah, would love to help out where I can. Thanks! |
@ryanhefner appreciate the ping - it's been a hectic few months! I've just added you as a maintainer. You should be able to manage issues/PRs/etc. now. Let me know if you run into any trouble! |
Hi @nwalters512,
I was just curious if you would like any help maintaining this package? There are a bunch of current PRs–including one of my own, #37–and dependency updates that could be done to keep this package up-to-date. I would be down to help out, if you would like. Also, if you are looking for someone to help maintain/take over the NPM package and maintenance, I am down to do that too.
Let me know if you are interested. This is a great package and has been useful in my work, and I would like to see it remain relevant and useful for me and others moving forward.
Thanks,
@ryanhefner
The text was updated successfully, but these errors were encountered: