Maintainers wanted #56
Comments
@fhemberger Hi! First off, thanks for creating this in the first place! I just used it on a project at work, worked like a charm. I appreciate all the effort here 🙏 I'd love to take on maintaining this, if that works for you. Happy to provide any info on my experience / background, if that's helpful to you in deciding. Let me know. Thanks! |
Hi again @fhemberger following up on the above: any interest in me taking on maintaining this going forward? Sorry to bug! I appreciate you're busy, don't mean to come across as entitled to your time. I'm bugging more because I know I'll lose track of this if I don't :) If the answer's just to be patient, I can do that, too Thanks! and have a great weekend |
Hi @zemccartney, sorry it took so long for me to reply. Happy to hear that you're interested in helping!
So really any help would be gladly appreciated. |
No worries at all! Thanks for getting back to me and for being open to me helping out. I'm excited to give it a go! That all sounds good. I'll start working on upgrading to v17. I'll shoot to get a PR for that in not too much time. If there's anything else you'd like me to handle or watch out for, just let me know. Thanks again! |
Getting v17 to work would already be super duper awesome. There isn't much to do otherwise. Thanks for your help! 👍 |
I haven't had the chance to work with hapi in general for a while now, so I'd like to hand over the project to someone who is more committed in maintaining it.
The project is considered feature complete, the only greater change I see right now is ensuring its compatibility with hapi's recent adaption of the async/await pattern.
So if anyone is interested, I'd be more than grateful to see this project thriving in a new home.
The text was updated successfully, but these errors were encountered: