-
Notifications
You must be signed in to change notification settings - Fork 29
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
Council: Who are the "deciders"? #173
Comments
it seems awkward to me to use the term "decider" when the Council itself is meant to make the decision. |
The intended meaning is that, given that a Formal Objection is against a decision, "the deciders" are whoever made or proposed the decision that is being objected to. If that meaning isn't obvious, rephrasing is certainly welcome.
Yes. WG for group decisions, chair for chair decisions, Team for Team decisions (including proposed charters)… |
One option would be to use "requesters", or just define "deciders" as Florian did above in plain text |
Adding the definition seems good enough to me. |
The definition could go in the paragraph above. This part
could change to something like: it is always better if there can be a consensus between the group that made the original decision and the objectors (we will use ‘deciders’ and ‘objectors’ to refer to these groups from this point) |
[[
This report is then sent to the W3C Council, to the deciders, and to the objectors. The Council, like the Team before it, may try to find a consensus path forward. Otherwise, the W3C Council uses input from the report, the deciders, and objectors to either overrule the objection (in which case the original decision is in force), or to sustain the objection (in which case the original decision is vacated).
]]
https://www.w3.org/Guide/council/council.html
It is not clear who the Deciders are (separate from the council). Is it different for different types of FOs. Perhaps Team for charters and the WG for WG decisions? Or just team/chairs for WG decisions?
(from @astearns)
cc @frivoal
The text was updated successfully, but these errors were encountered: