tjfontaine / native-dns-packet

DNS parsing and writing in javascript
MIT License
58 stars 36 forks source link

New Maintainer? #33

Open techguy613 opened 8 years ago

techguy613 commented 8 years ago

I noticed that there is an ongoing discussion in node-dns about finding a new maintainer. Has anyone stepped up to the plate on that one and would that also include this repo? There so many PRs waiting to be merged (at least one of which I really need to either include, or create my own repo and package) to be able to finalize a DNSSEC resolver I've ported to JS.

If no one is interested, I would be ok with maintaining this repo.

Thanks,

-- Matt

techguy613 commented 8 years ago

Hey all, I wanted to follow-up on this one. Does anyone have an opinion on this either way? If not, I would love to get maintenance on this repo going again as a maintainer.

harshjv commented 7 years ago

Any update?

techguy613 commented 7 years ago

Any word on this? I would love to get active contributions back on this library.

taoeffect commented 7 years ago

@techguy613 So per https://github.com/tjfontaine/node-dns/issues/111 — since @tjfontaine is AWOL & unresponsive, and since I only have push rights (not admin rights), the way forward is for someone to create a fork of both projects, give them new names (for NPM publishing), and reply here in a comment demonstrating that their fork is:

  1. Actively maintained.
  2. Has dealt with the open PRs properly.
  3. Is of at least as good quality as the present unmaintained repos.

If such a fork satisfies the criteria above, I will update the READMEs on both projects to point folks to the new fork.