Escalation strategy

In their July meeting the Foundation TAC discussed a potential escalation policy for issues that might need input from the TACs. The process would be generally bottom-up and would start on GitHub:

1. If an issue, PR or discussion thread could benefit from input from the TACs, anyone with triage access to the repository can apply a label to indicate a desire for the TACs to consider it. (The label could be something like tac feedback requested.)
2. Depending on the nature of the issue, it might be useful to move aspects of the discussion to a proposed General Discussion area on the Communities site. That way we could avoid, for instance, overwhelming a PR with meta discussion that goes beyond the proposed change and could be off-putting to a first-time PR author.
3. Members of the TACs might take the discussion to the specific communities they represent, if they deem that helpful for the question at hand.
4. The TACs could consider the issue in a regular meeting, in an asynchronous discussion and/or put it to a vote, as appropriate for the specific question.
5. Some questions might need to be further escalated to the Corporation and Foundation directors.
6. Once the question has been resolved, the label would be removed.

This is a rough sketch so that we have something to talk about. When we have a more fleshed-out proposal, it would be helpful to present it to the Corporation BAC for consideration.