@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 here's how i'm thinking about it

let's say my literal actual job is to maintain some project. if i am to keep up with the community engagement, i need to at least split "my job description" vs "community efforts" as 50/50, but sometimes it's closer to 25/75

and i don't think microsoft, or really anybody else, considers does that

@malwareminigun this is the situation i was in with Amaranth and it generated a pretty big amount of friction with the management (and is a big part of why i eventually left and got an NLnet grant to continue doing so)

though unlike that startup, Microsoft has functionally infinite cash

@whitequark At the moment my job description is about 70% keep the community from collapsing 30% prevent us from getting sued into oblivion.

RE: Infinite cash: You and I are together in screaming at the company to fund things; as it is vcpkg is down to effectively 2 heads.