Thanks for doing this analysis Tom!
I don’t think any of those people were chosen purely on their triage abilities. I think they were mostly picked for their review abilities. I say this because many of the T&R team don’t show up doing any triage at all, but every single one of them reviews PRs and I believe they’ve all made their own code contributions as well.
I’m a member of the Triage and Review team and I’m pretty sure in my case that’s based on review rather than triage, for the most part. For those times I’ve been involved in triage it’s been as a navigator for Djangonaut space or as a interested reader of a forum post.
Either way, we end up at a maximum of 1.3% well-handled community triage over the last year. I’m not sure that seems to be worth holding onto at all costs.
I think this is right. I think people good at triage are likely to put the results of their triage work in a comment on the issue, even if they don’t have permissions to update flags or close the issue. If we move to another platform we can keep an eye out for people to trust with these permissions. Depending on the permissions, we might be able to be very open with giving them - someone assigning the wrong labels or closing an issue incorrectly is easily fixed.