8000 Require documentation of how FOs get resolved by frivoal · Pull Request #953 · w3c/process · GitHub
[go: up one dir, main page]
Skip to content

Require documentation of how FOs get resolved #953

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Dec 23, 2024
Merged

Require documentation of how FOs get resolved #953

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Require documentation of hwo FOs get resolved 
See #870
  • Loading branch information
@frivoal
frivoal committed Dec 6, 2024
commit ef07d0d517b676e8d5ffd30b2854a8d1d24be5a9
3 changes: 3 additions & 0 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2388,6 +2388,9 @@ Registering Formal Objections</h3>

Registering a [=Formal Objection=] initiates the process of
[[#addressing-fo|addressing the Formal Objection]].
The resolution of a recorded Formal Objection--
whether by a Council decision, adoption of a consensus proposal, retraction of the Formal Objection, etc.--
must be recorded and made available at the same level of visibility as the record of the Formal Objection itself.

<h3 id=addressing-fo>
Addressing Formal Objections</h3>
Expand Down
0