-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[template] time to add the TAG design principles #303
Comments
Sounds premature. When does TAG plan to share these design principles more widely/formally? |
I hear from a TAG member that the Process Document does not allow the TAG to publish on /TR !! w3c/process#429 Which makes it hard to share more formally. TAG reviews regularly use these design principles though. |
Given response from TAG, and also confirmation that WHATWG already follows them, I plan to add this to the template. |
Let's discuss |
This was fixed in Process 2021
If the question is "when will they be done" then the answer is that they are taking a living standard approach and the principles are continuously evolving. If the question is "when is it appropriate to cite them" then Horizontal Review already includes TAG review, which includes checking the box that the Design Principles have been read. If work is going to fail TAG review due to breaking the TAG design principles then it seems that charters should by default include wording that the WG intends to follow them. |
Since this has been Agenda+ for 18 months without actually being discussed, I raised an issue on the TAG design principles repo: |
Closed since the TAG agreed that charters should include an expectation to follow these, so I added it to the template. |
The document is still being worked on, but I wonder if it is time to add something like
The text was updated successfully, but these errors were encountered: