Council decision side effects
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- documentation
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.
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.
- Dominant language
- HTML
- Stars
- 263
- Forks
- 193
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/process
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Agenda+
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Agenda+
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Type: Enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Type: Enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
resend/resend-skills#144 ·
Maintainers usually reply within 1 day
-
backend
Difficulty 1/5 Under an hour Newbie friendliness 95/100
PedestrianDynamics/pyFDS-Evac#540 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
openzfs/openzfs-docs#650 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
supabase/agent-skills#619 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
gravitational/teleport#69827 ·
Maintainers usually reply within 11 days