From 835e9ff5049568f7c41f7c5f4b0bfc3c1477490b Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Tue, 22 Oct 2024 14:12:38 +0900 Subject: [PATCH] Streamline Council formation and provide safeguards (#925) A major source of dissatisfaction with the current Formal Objection handling process is the time it takes to initiate Councils. This brings the following improvements: * This makes it clear that the administrative steps for forming a council are expected to happen in parallel with the Team's effort to resolve and/or document the objection, which should cut the waiting time (and matches what the Team is moving towards anyway). * Currently convening a Council *must* start within 90 days of FO registration, and *should* be complete within an extra 45 days. not only is this long, it means there is no actual hard end date. After this change, the hard deadline is 90 days. * Previously, nothing happened if the deadlines were exceeded. This empowers the AB and TAG chairs to complete council formation once we're past the deadlines. Co-authored-by: Ted Thibodeau Jr --- index.bs | 37 ++++++++++++++++++++++++++----------- 1 file changed, 26 insertions(+), 11 deletions(-) diff --git a/index.bs b/index.bs index 25bf44b3..ab040e60 100644 --- a/index.bs +++ b/index.bs @@ -2402,6 +2402,10 @@ Investigation and Mediation by the Team to make sure the problem and the various viewpoints are well understood, and to the extent possible, to arrive at a recommended disposition. + + In parallel, the Team should start the steps necessary + to convene a Council. + If the [=Team=] can resolve the issue to the satisfaction of the individual that filed the [=Formal Objection=], the individual withdraws the objection and the disposition process terminates. @@ -2409,10 +2413,10 @@ Investigation and Mediation by the Team Otherwise, upon concluding that consensus cannot be found, and no later than 90 days after the [=Formal Objection=] being registered, - the [=Team=] must initiate formation of a [=W3C Council=], - which should be convened within 45 days of being initiated. - Concurrently, it must prepare a report for the [=Council=] - documenting its findings and attempts to find consensus. + the [=Team=] must + deliver to the [=Council=] a report + documenting its findings and attempts to find consensus, + and hand over the matter to the [=W3C Council=].

W3C Council

@@ -2563,16 +2567,27 @@ Council Chairing if requested by the [=Council Team Contact=] or by the [=Chair=] during the Council’s operation. -
-Council Deliberations
+
+Convening the Council
-

Upon appointment of the [=W3C Council Chair=] and delivery of the [=Team=]’s report, - the [=W3C Council=] is considered to be convened - and can start deliberations. + the [=W3C Council=] is considered to be convened + and can start [[#council-deliberations|deliberations]]. + + If a [=W3C Council=] has not yet been [=convened=] within 90 days of a Formal Objection + being [[#registering-objections|registered]], + the [=Chairs=] of the [=TAG=] and [=AB=] may take independent action to ensure + that the [=dismissal=], [=renunciation=], + and [[#council-chairing|chair selection]] processes have been run. + If a report from the Team is not delivered within those 90 days, + the [=Council=] is considered [=convened=] + upon selection of the [=W3C Council Chair|Council Chair=]. + +

+Council Deliberations
- Having reviewed the information gathered by the [=Team=], + Once [=convened=], the Council may conduct additional research or analysis, or request additional information or interviews from anyone, including the Team. @@ -2634,7 +2649,7 @@ Council Deliberations and its [=Council Team Contact=].

- If a [=W3C Council=] is unable to come to a conclusion within 45 days of being convened, + If a [=W3C Council=] is unable to come to a conclusion within 45 days of being [=convened=], the [=W3C Council Chair=] must inform the [=AC=] of this delay and of the status of the discussions. The [=W3C Council Chair=] may additionally make this report public.