Skip to content

Council Guide and AC reviews #176

Open
@chrisn

Description

The Council Guide says "groups work hard to understand different points of view" and "When that is working well, Formal Objections are rare, indeed". This gererally applies to decisions made in WGs, but not to AC charter reviews - where there is no real discussion among the AC and the only way to express dissent is via Formal Objection, so this should be reflected in the Guide.

Similarly, "implies that before an objection gets a senior review there already has been a great deal of work on the issue" may apply to WG decisions but not AC charter reviews.

"The objector, in trying to reverse the decision, has generally pulled together their best arguments and brought them to the group." As we have seen with some AC charter reviews, these can be very short, and there's no requirement for AC reviewers to bring their comments to the WG.

"There is generally clarity on what the W3C decision was" - in Process 2023, formally, a W3C Decision follows an AC review, so I suggest amending this text to clarify the different kinds of decisions.

Finally, a minor point, but I would prefer to avoid the word "senior", the groups involved (a WG, the AC, the AB, TAG, Team) each have different roles, but one isn't necessarily senior to another.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementThe specification works as-is but could be improved.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions