You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 44774e6
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: process/charter.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,7 +129,7 @@ All issues filed against the charter draft during refinement must be formally ad
129
129
130
130
### 3.4 Requesting a TiLT decision
131
131
132
-
Before the end of the announced duration for the charter refinement phase, The Technical Strategy Team (represented by the Technical Leadership Team, or TiLT and informed by the work of the Chartering Facilitator) must decide which of the following to do:
132
+
Before the end of the announced duration for the charter refinement phase, the Technical Strategy Team (represented by the Technical Leadership Team, or TiLT and informed by the work of the Chartering Facilitator) must decide which of the following to do:
133
133
134
134
* Complete charter refinement by initiating AC Review of the charter draft.
135
135
* Abandon the proposal.
@@ -213,6 +213,7 @@ Request extension notice
213
213
214
214
Let the group know
215
215
: The W3C Communications Team inform the group that its charter has been extended.
216
+
: The W3C Communications Team proceeds with task #4 of [announce extension](https://www.w3.org/policies/process/#announce-extension).
216
217
217
218
### 4.2 Request for rechartering {#recharter-request}
218
219
@@ -425,10 +426,10 @@ When requesting that the W3C Communications Team announce a charter extension, u
425
426
426
427
The W3C Communications Team then:
427
428
428
-
- Sends extension announcements to w3c-ac-members@w3.org
429
-
- ... and later forwards the announcements as FYI to chairs@w3.org
430
-
- It is a good practice to forward the extension announcement to the public list of the group, and to follow-up on public-new-work.
431
-
- updates the [list of groups](https://www.w3.org/groups/) accordingly.
429
+
1. Sends extension announcements to w3c-ac-members@w3.org
430
+
2. ... and later forwards the announcements as FYI to chairs@w3.org
431
+
3. It is a good practice to forward the extension announcement to the public list of the group, and to follow-up on public-new-work.
432
+
4. Adds the charter extension via the [Groups DB](https://www.w3.org/admin/dashboard) interface.
432
433
433
434
The Communications Team modifies (or asks the Staff Contact) the Charter in place as follows:
434
435
@@ -445,6 +446,7 @@ When a group **Chair** is (re)appointed or resigns, shortly before/after the ann
445
446
446
447
## 6. Revision history {#revision-history}
447
448
449
+
- **2026-10**: Editorial: added missing step after short extension of charter is granted; updated links to groups DB interface.
448
450
- **2025-08**: Overhauled to integrate charter refinement introduced in the 2025 Process Document.
449
451
- **2024-01**: Public comments and Formal Objections (including from Members) are now to be sent to public-review-comments@w3.org; various editorial changes.
450
452
- **2023-10**: Updated following Process 2023 and reorganized to separate high-level processes from implementation.
0 commit comments