Document how to get the attention of an horizontal group in order to close horizontal issues

[plehegar]

We need guidance to groups on how to properly communicate with horizontal groups when attempting to close horizontal issues. As usual, a Group is allowed to time out and attempts to move forward anyway, but a Group should not rely on the Director to get the attention of an horizontal Group in order to close the loop on horizontal issues.

The use case is:

The Group responded to an horizontal comment but never heard back from the horizontal group. The Group either believe they addressed the issue but didn't get confirmation that it was resolved, or they responded to the comment but are still unsure on how to move forward.

Attempting to capture my understanding on how to communicate:

For PING, communicate with public-privacy@w3.org (from @samuelweiler ).
For i18n, communicate with member-i18n-core@w3.org (from @r12a).
For APA, is it public-apa@w3.org (question for @michael-n-cooper )
For Security, what is it?
For TAG, what is it? (question for @ylafon )

[michael-n-cooper]

For APA, I suggest sending administrative questions about status of reviews to group-apa-chairs@w3.org. Note that for issues turning up in the a11y-request and a11y-review repositories, I put comments about review status when there's something to say, and close the issue when we consider it fully resolved.

[ylafon]

For the TAG it depends if the group wanted feedback in their own repo or on the TAG's design-review issue.
In any case to get TAG's attention, the best would be to ping on the TAG review issue, optionally pinging the chairs in it.

[r12a]

The Group responded to an horizontal comment but never heard back from the horizontal group. The Group either believe they addressed the issue but didn't get confirmation that it was resolved, or they responded to the comment but are still unsure on how to move forward.

This seems to suggest that separate emails are sent for each of the review comments. I hope that won't happen. I think the use case is actually that the WG needs to check the HR group's tracker repo for any issues that remain open (i think its important to explicitly mention that, since that's what the Director will look at), and send an email to prompt the HR group to clarify the status of those. (Such an email, by the way, is likely to be very helpful to the HR group, because it will prompt them to tidy up their repo and help them prioritise their workload.)

It's probably also worth advising the WG that the sooner this is done, the better, since we don't want unexpectedly protracted discussions to delay the transition. The HR group may also be unable to drop everything immediately to focus on the WG's issues.