-
Notifications
You must be signed in to change notification settings - Fork 132
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
Link to document on formal objection processing #337
Comments
astonishingly, the process says nothing at all about processing FOs, only about recording and reporting them. We probably need a short section somewhere. I'd rather not deprecate; when we go Dir-Free, we'll need an improved version of this. |
For Director-free, the AB has been working on a draft improved version of this: https://www.w3.org/2019/06/W3C%20Council%20guidelines%20for%20formal-objections.html |
@samuelweiler, The whole handling of formal objections is being reconsidered, in order to figure out how to make it work in a director-free w3c. In the present state of things, the suggestion you're making here seems reasonable, but I am not sure we want to draw attention to things that are about to change, so I'd rather defer this issue. Are you ok with that? |
Closing as out of scope in favor of w3c/Guide#166 |
Add an in-line informative reference to: https://www.w3.org/2017/12/formal-objections.html
(Alternatively, deprecate that document.)
The text was updated successfully, but these errors were encountered: