w3c / w3c/guide

Council Guide and AC reviews

Open
#176 2 comments 0 reactions 1 assignee View on GitHub

@ylafon is already working on this.

Since Sep 25, 2023.

enhancement
Dominant language
HTML
Stars
84
Forks
69
Avg merge
14h 52m
Merged PRs (30d)
2

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.