monthly routine ^_^

@whitequark I feel so conflicted about this. On the one hand I agree with you the situation sucks. On the other hand we have deployed this because we get tends of thousands of meaningless garbage issue reports and we can barely keep up with incoming PR submissions, much less issue submissions.

I guess maybe there's an argument that we shouldn't have issue tracking turned on at all if we can't meaningfully look at them but they're occasionally useful for coordinating something that happens across several PRs.

@malwareminigun can you set ACLs so that only project members can file issues?
@whitequark Doesn't look like it. The only options I see in here are "enable/disable issues" and "enable/disable closing issues based on keywords in PRs/commit messages".
@malwareminigun right yeah so... that's on github. I think I would not be upset if I encountered auto-closing issues instantly with a message that boils down to "we simply do not have resources to deal with this" (this is better than just letting it to rot); it's really the uncertainty and repeated make-work that's a problem in the original case