Skip to content
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 Guide and AC reviews #176

Open
chrisn opened this issue May 24, 2023 · 2 comments
Open

Council Guide and AC reviews #176

chrisn opened this issue May 24, 2023 · 2 comments
Assignees
Labels
enhancement The specification works as-is but could be improved.

Comments

@chrisn
Copy link
Member

chrisn commented May 24, 2023

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.

@plehegar plehegar added the enhancement The specification works as-is but could be improved. label Sep 25, 2023
@ylafon
Copy link
Member

ylafon commented Oct 10, 2023

I agree that often, the discussion around charters happens with Formal Objection, however, there is the advance notice system that gives pointers to start a discussion, usually on the charter GH repository.

The current Council Guide text says

Similarly, most Working Group Charters are openly developed in Github. Advanced Notices inform the community when there is a new Charter to look at, the Charter development process is open for people to raise issues and there is a fair effort to resolve issues prior to someone raising a Formal Objection.

So I wonder if the Guide should amended, or the way communication around advance notices / pre-vote review should be better.

Re: senior: would deeper review be better?

@chrisn
Copy link
Member Author

chrisn commented Oct 12, 2023

So I wonder if the Guide should amended, or the way communication around advance notices / pre-vote review should be better.

I think improving pre-vote review would be a good thing. There was discussion on chartering at TPAC (minutes) and I think the AB plans to follow up, so perhaps we should leave it until that happens.

Re: senior: would deeper review be better?

Or "Council review"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The specification works as-is but could be improved.
Projects
None yet
Development

No branches or pull requests

3 participants