Close pull requests that won't be merged about hickory

[njordhov]

As a contributor, I second that more feedback would be helpful. It seemed that my PR #33 was on track to be merged, but it has been in limbo for a while even if the PR would remove a bottleneck for using hickory dependents on Node.

[davidsantiago]

Yeah, Maybe you're right. My feeling has always been that they're there if the original requester wants to pick it back up, or if someone else wants to come along and do the work.

[ricardojmendez]

or if someone else wants to come along and do the work.

I'd say that's a reasonable expectation if it's an issue, but for a PR, either it's merged or it isn't. If someone's considering submitting a new one, and they see PRs open from 2014 in 2016, it gives the impression the project's not following up.

How about adding a note to see if the submitter wants to bring them up to speed, and otherwise just close them after X time of radio silence? Might not even be clear to the submitter what the requirements for acceptance are.

[port19x]

100% agree with the sentiment, will work on it

[port19x]

Not sure how to proceed with #35, but it's plausible enough to leave open