Spin off from ticket
CLDT TC meeting notes Dec 12, 2018
Two kinds of tickets fixed by TC votes — or XML change.
Policy decision — want it to stick no matter what users say (flagged in future). Requires feedback, long discussion. (relatively few).
This ticket is to design a tools solution to handle TC votes that were done based on policy decision.
The design should include:
1. How to identify TC votes per policy.
2. An ability to capture the policy description (i.e. explain why)
3. An ability to flag to vetters that this is not changeable per policy decision.
4. Vetters can open tickets if they have a dispute to the policy decision.