w3c / w3c/process

Council decision side effects

Open
#751 23 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

FO/Council
Dominant language
HTML
Stars
262
Forks
194
PR merge metrics
No merged PRs in 30d

Description

When sustaining an objection, it should recommend a way forward. If the overturned decision has already had consequences (e.g., if the objection concerns material already in a published document) the Council should suggest how these consequences might be mitigated. The Team is responsible for making sure that adequate mitigations are enacted in a timely fashion; and the Formal Objection is not considered fully addressed until then.

This attaches new and relatively unconstrainted powers to the Council -- what is the status of their 'recommendations' and 'mitigations'? Are the required to be followed? If they have unanticiapted side effects on other matters that have consensus, can they be appealed?

The safest thing to do would be to remove this text and only empower the Council to give a thumbs up/down. Failing that, stating that the recommentations are to the WG are suggestions for further consideration, without formal standing would help. Any mitigations that require Team action should be limited to those activities which the Team has authority to perform.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the linked Process Draft sections on sustaining an objection, the Team, and Formal Objection, then review the 23-comment thread for its unresolved decision. Done means the Council’s recommendation and mitigation powers have agreed wording in the Process document; the issue names no file or test to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.