-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add Team procedures for FO and Councils #245
Open
ylafon
wants to merge
5
commits into
w3c:main
Choose a base branch
from
ylafon:fo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
8b6c7b2
first draft, might be converted to a state diagram
ylafon ef6c616
missed ML step
ylafon 764866c
Update council/council-steps.html
ylafon 2b4cc75
clarify who updates those pages
ylafon 0e9c051
Update council/council-steps.html
ylafon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,106 @@ | ||
<!DOCTYPE html> | ||
<html lang="en"> | ||
<head> | ||
<meta charset="utf-8" > | ||
<title>Formal Objections: From Objection to W3C Council</title> | ||
<link rel="stylesheet" href="/StyleSheets/generic-base-1.css" type="text/css"> | ||
<link rel="stylesheet" type="text/css" href="../assets/main.css"> | ||
<link rel="shortcut icon" href="/Icons/WWW/Literature.gif"> | ||
<link rel="start" href="../" > | ||
<style> | ||
.IssueLabel-big { | ||
font-weight: 600; | ||
padding: 4px 8px; | ||
border-radius: 3px; | ||
line-height: 1.5; | ||
box-sizing: border-box; | ||
text-decoration: none; | ||
} | ||
</style> | ||
</head> | ||
<body> | ||
|
||
<div id="header"> | ||
<span class="logo"><a href="/"><img src="/Icons/WWW/w3c_home_nb" | ||
alt="W3C" height="48" width="72"></a></span> | ||
<div class="breadcrumb"> | ||
<a href="/Member/">Member</a> → <a href="/Guide/">The Art of | ||
Consensus</a> → | ||
<h1>Formal Objections: From Objection to W3C Council</h1> | ||
</div> | ||
<p class="baseline">This <strong>Guidebook</strong> documents the possible steps from Formal Objection to the creation of a W3C Council.</p> | ||
</div> | ||
|
||
<div class="toolbox box"> | ||
<h4>Nearby</h4> | ||
<ul> | ||
<li> | ||
<a href="https://www.w3.org/Guide/council/council.html">Formal Objections & W3C Council</a> | ||
</li> | ||
<li> | ||
<a href="https://www.w3.org/Member/wiki/DirectorFOdashboard">Formal Objection dashboard</a> (Member-only link) | ||
</li> | ||
<li> | ||
<a href="/policies/process/">W3C Process Document</a> | ||
</li> | ||
<li> | ||
<a href="https://lists.w3.org/Archives/Public/public-new-work/">Archives of new work advance notices</a> | ||
</li> | ||
<li> | ||
<a href="https://lists.w3.org/Archives/Public/public-review-comments/">Archives of public comments and formal objections</a> | ||
</li> | ||
<li> | ||
<a href="/policies/code-of-conduct/">W3C Code of Conduct</a> | ||
</li> | ||
</ul> | ||
</div> | ||
|
||
<div id="Content"> | ||
<p>This document describes the different steps to resolve a Formal Objection. It should be kept synchronized with the <a href="https://www.w3.org/policies/process/">W3C Process Document</a> which is the authoritative source.</p> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It should also stay in sync with https://www.w3.org/Guide/council/council |
||
|
||
<p>Note that at any step, the whole process might end by the originator by withdrawing the Formal Objection. This is the best outcome and should always be sought</p> | ||
<ol> | ||
<li>Formal Objection received</li> | ||
<li>The Team Contact tries to resolve the Formal Objection before starting the process.</li> | ||
<li>The FO stands: The Team assigns a "FO Assignee" to handle the Formal Objection. Note that is is not always the Team Contact, but someone having knowledge of the issue raised in the FO.</li> | ||
<li>The FO Assignee request a Council to <a href="https://github.com/w3c/tilt-private/issues">TiLT</a> (Team-only link). In parallel: | ||
<ul> | ||
<li>The FO Assignee start a Team Report.</li> | ||
<li>The Team Report is circulated to the Team for review (one week review time)</li> | ||
<li>The Team Report is circulated (at the same time or after Team review) to both parties.</li> | ||
</ul> | ||
</li> | ||
<li>TiLT approves the Council</li> | ||
<li>The FO Assignee updates the <a href="https://www.w3.org/Member/wiki/DirectorFOdashboard">Formal Objection dashboard</a>.</li> | ||
<li>The Council Team Contact drafts an announcement and call for dismissal reasons with a minimum deadline of two weeks (See this <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2024JanMar/0021.html">example</a>, and the <a href="https://www.w3.org/policies/process/#council-composition">Council composition</a>). | ||
<ul> | ||
<li>Announcement is sent to the AC members list</li> | ||
</ul> | ||
</li> | ||
<li>The Council Team Contact creates a new <a href="https://www.w3.org/admin/othergroups/list">Group</a> (name should be <em>Council-YYYY-MM-<readable shortname></em>) in the db, filled with all the potential members of this Potential Council</li> | ||
<li>The Council Team Contact creates a new <a href="https://www.w3.org/Systems/Mail/Request/">Mailing List</a>) (name should be <em>group-council-YYYY-MM-<readable shortname></em>)</li> | ||
<li>The Council Team Contact tries to find a Chair for the Potential Council</li> | ||
<li>The Council Team contact circulates the collected dismissal reasons to the Potential Council (1 week to amend or answer)</li> | ||
<li>The Council Team contact circulates the Team Report while point above is discussed</li> | ||
<li>The Council Team contact create a WBS for dismissal, with the option to self-recuse, and accept the Chair, if found; if not ask for chairs.</li> | ||
<li>If the Team Report contains a Team Recommendation that can resolve the FO: | ||
<ul> | ||
<li>The Council Team contact create a WBS for an <a href="https://www.w3.org/policies/process/#council-short-circuit">Unanimous Short Ciruit</a></li> | ||
<li>TAG and AB Team contact to ensure that <em>everyone</em> is voting</li> | ||
<li>If the USC succeed, the Council is not formed and the resolution is accepted</li> | ||
</ul> | ||
<li>If the chair is not found, the Potential Council elects one chair</li> | ||
<li>If the chair is found: | ||
<ul> | ||
<li>The Council Team contact announce with Comm the composition of the Council to the AC</li> | ||
<li>The Council Team contact announce to the Council that the Council started</li> | ||
<li>The Council Team contact update the FO Dashboard to indicate that the Council started</li> | ||
</ul> | ||
</li> | ||
<li>The Council chair[s] (and Council Team contact) may start an <a href="https://www.w3.org/policies/process/#council-delegation">Extraordinary Delegation</a> WBS</li> | ||
<li>The Council takes a decision</li> | ||
<li>The Council writes a report</li> | ||
<li>The Council Team Contact ensures that the <a href="https://www.w3.org/about/council/">W3C Council</a> as well as the FO Dashboard are updated</li> | ||
<li>The decision is announced to the different parties and the AC</li> | ||
</ol> | ||
</div> |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
meta comment: since we're adding documentation about Team internal procedures into /Guide (like TilT), we should probably make those pages are not expected to be followed by non-Team folks.