Reuse of this infrastructure for some other forms of cross-group issue tracking

[hober]

(TAG and HTML WG hats off, but nearby)

I think this new cross-group issue tracking infrastructure is really great. I'd love it if we could also consider using it for groups which are not W3C Horizontal Review groups but who nevertheless need to track a lot of issues on a lot of specs in other places, e.g. for the WHATWG to track issues in various W3C specs related to integration with HTML, Fetch, etc.

I think this would help us (in a very broad sense of "us") to all work together better, in the spirit of the MoU.

(I had this thought while @dbaron filed w3c/csswg-drafts#5115 today.)

[hober]

Maybe non-horizontal review groups who which to reuse this infrastructure get -tracker labels, but not -needs-resolution ones.

[hober]

Another recent example: we used htmlwg-tracker and htmlwg-needs-resolution labels in the @w3ctag to track our recent horizontal review of HTML within TAG repos.

[plehegar]

I'm still mulling this one.

The proposed solution increases the number of GH labels for all of our spec repositories significantly.

We're adding 10 labels today (2 for each of the 4 HR Groups + TAG) and someone already mentioned getting overwhelmed a bit. In addition, we're giving triage rights to team contacts and chairs of those Groups to all spec repos (including WHATWG repos).

We have 34 WGs so that would add at least 34 labels and a lot of folks would get triage rights...