Skip to content

Commit

Permalink
Considerations for publishing formal objections. (#222)
Browse files Browse the repository at this point in the history
Address w3c/process#735 
 following w3c/process#808

---------

Co-authored-by: Ted Thibodeau Jr <[email protected]>
  • Loading branch information
plehegar and TallTed authored Apr 25, 2024
1 parent f7c0927 commit 8bf53f8
Showing 1 changed file with 38 additions and 0 deletions.
38 changes: 38 additions & 0 deletions council/council.html
Original file line number Diff line number Diff line change
Expand Up @@ -156,6 +156,44 @@ <h3 id="team-fo"><a href="#team-fo">Team attempts to resolve Formal Objections</

<p>See also: <a href="https://www.w3.org/Member/wiki/DirectorFOdashboard#Team_is_attempting_to_find_consensus_or_not_ready_to_ask_a_Council">Ongoing Team Attempts</a></p>

<h3 id="publishing-fos"><a href="#publishing-fos">Publishing formal objections</a></h2>

<p>
Formal objections must be made public using <a
href='https://lists.w3.org/Archives/Public/public-review-comments/'>public-review-comments</a>, no later than when the
relevant council is initiated. The team should publish formal objections as soon as
reasonable within the 90 days investigation and mediation period, with some
considerations including:
</p>
<ul>
<li>all Formal Objections must be published, even those that are expected to
be — or have already been — withdrawn.
</li>
<li>the Formal Objection ought to be made public as soon as it is
received if it needs to be discussed by a <a
href='https://www.w3.org/groups/'>W3C Group</a>.
</li>
<li>
to avoid unproductive attention on members who file formal objections
on easily resolved matters such as charter durations and the like, the Team should
anonymize such formal objections as a matter of routine.
</li>
<li>
If there are multiple Formal Objections to the same decision or to the same AC Review,
the Team should make them all public at the same time, to avoid attracting unwarranted
unbalanced media attention to a single objector among several. For the same reason, if
some formal objections are already public — for instance, if the objector made it
public themselves — the Team should make any other formal objection to the same decision or
to the same AC Review public without delay.
</li>
</ul>

<p>
To avoid leaving people wondering what happened, the Team should post a response to the
announcement of the formal objection, indicating the resolution of the formal objection,
such as overruled or withdrawn, and giving a quick summary as to why.
</p>

<h2 id="referral"><a href="#referral">Referral to W3C Council</a></h2>

<p>If resolution is not possible in the allocated time frame, the assignee must refer the Formal Objection to the W3C Council for decision. The steps for that are as follows:</p>
Expand Down

0 comments on commit 8bf53f8

Please sign in to comment.