Publish new Release?

[rsandor]

Seems it has been a while since a new release was published on npm. Specifically I'd like callback support for .serve on the server implementation.

Thanks for the great package!

[taoeffect]

I could use some help maintaining this package, as lately I simply haven't had enough time available to devote to it. @tjfontaine, feel free to suggest folks.

cc @greggman @sindresorhus @bobvanderlinden

[rsandor]

I can help if you need, we are using your package a lot at work. Let me know :)

[bobvanderlinden]

I'm sad to say I don't work on a project that actively uses node-dns anymore, so there is little real motivation from me to keep things going :( (I'm probably in a similar boat as @taoeffect). The previous project was using a custom build of node-dns to get the recent features/fixes at the time, so I can imagine a release being be nice for others.

@taoeffect I suggest somehow allowing a select few others to manage the project. Maybe make an organization and transfer the project to it? It's a one-time investment, after that things will run with help of @rsandor and hopefully others. Same goes for https://github.com/tjfontaine/native-dns-packet

There are a bunch of PRs that are needed before publishing the release, like fixing the unit tests imo, so this isn't just doing a release ;).

[rsandor]

Let me set aside some time this week to go through the issues, get deeper into the code, and cross-reference with native-dns-packet. If it looks like I can really dig in, I will just start opening PRs that address issues.

[taoeffect]

@rsandor Awesome. Please have a look at this comment to see what review help is needed right now.

@tjfontaine could you please comment on @bobvanderlinden's suggestion above? And what do you think about adding @rsandor to the project? This is your project, not mine. I am not able to add others as admins to this project, nor would I want to without your permission to do that.

[bcoe]

@tjfontaine @taoeffect could you publish an update this module, or perhaps add @sindresorhus or myself as maintainers?

There's some exception handling behavior causing problems with public-ip, which I'd love to start using for a project at npm.

[taoeffect]

@bcoe I do not have the permissions necessary to add anyone as a maintainer, but I will try pinging @tjfontaine via DM.

[taoeffect]

@bcoe, if @tjfontaine doesn't get back to you within 1 week as of this comment, the best course of action would be to fork this repo and publish the new "native-dns" under a new name. I would support that.

[taoeffect]

Two days left for @tjfontaine to reply. @bcoe, has he contacted you?

If no reply in two days, then once a new fork is created under a different name (that proves stable), I will update the README with a link to it and declare this project deprecated.

[taoeffect]

Join us in the search for a winning fork!