Audit of old repo issues

[Henry Andrews]

Hi folks,

  As promised, I have gone through and audited the issues filed at the old repo.  Here are my thoughts on them:

https://docs.google.com/spreadsheets/d/1pcT638kI7vrY4MjWxgMKUVpjuwceC9EtRuCcHldzB5c/edit?usp=sharing

As best I can tell, a great many of them can and should be closed as they are resolved.  The questions that have been answered and concrete bugs that have been fixed are the most obvious (I also submitted a few pull requests to the new spec repo for easy fixes that I could see).

Furthermore, there are several that are pretty clearly out of scope for JSON Schema (at least if I properly understand the scope of this project).

I'd argue that some discussions, while they made sense to start in issues, don't make sense to continue tracking in issues (the large-scale project of moving to the new repos being a prime example, also the open-ended "reboot IETF thinking" issue).

Some of the larger proposals seem to have been rejected or accepted- is there a clear way to confirm such resolution and take action?

Most of the proposals, of course, need resolution, so I would be inclined to correlate them with the proposals on the wiki and file the minimum number of issues to cover all of the proposals.  Many of the issues eventually converge onto the same topics and should be consolidated.

Does anyone here have the ability to close issues on the old repo?

thanks,

-henry