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
Copy file name to clipboardExpand all lines: process/charter.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,15 +33,15 @@ Within the chartering process, the following are [Team Decisions](https://www.w3
33
33
34
34
In practice, the Team delegates these Team Decisions to the [Technical Strategy Team](https://www.w3.org/staff/strat/), which manages the charter development process, including allocation of staff resources.
35
35
36
-
The Technical Strategy Team tracks charters through the process via the [W3C Technical Strategy Pipeline](https://github.com/orgs/w3c/projects/97/views/2) (or "pipeline" in this document). A dashboard of [Charters in development](https://www.w3.org/2024/03/charters-in-dev.html) is also available.
36
+
The [Technical Strategy Team](https://www.w3.org/staff/strat/) and [Project & Process Team](https://www.w3.org/staff/project/) track charters through the process via the [W3C Technical Strategy Pipeline](https://github.com/orgs/w3c/projects/97/views/2) (or "pipeline" in this document). A dashboard of [Charters in development](https://www.w3.org/2024/03/charters-in-dev.html) is also available.
37
37
{:#pipeline}
38
38
39
39
### 2.2 Chartering Facilitator
40
40
{:#chartering-facilitator}
41
41
42
-
The Technical Strategy Team Lead chooses (and may replace) a *Chartering Facilitator* to shepherd a given charter through the process. The Chartering Facilitator is typically from the Staff but is not required to be from the Staff. In the case of rechartering it is common to n
8000
ame the group's [Staff Contact](../teamcontact/role.md) as the Chartering Facilitator.
42
+
The [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) and/or [Project & Process Team Lead](https://www.w3.org/staff/project/) choose (and may replace) a *Chartering Facilitator* to shepherd a given charter through the process. The Chartering Facilitator is typically from the Staff but is not required to be from the Staff. In the case of rechartering it is common to name the group's [Staff Contact](../teamcontact/role.md) as the Chartering Facilitator.
43
43
44
-
**Note:** If the Technical Strategy Team Lead cannot identify a Chartering Facilitator, there may be delays in advancing the charter through the process.
44
+
**Note:** If the Team Leads cannot identify a Chartering Facilitator, there may be delays in advancing the charter through the process.
45
45
46
46
### 2.3 Charter assessment criteria
47
47
{:#charter-assessment-criteria}
@@ -92,16 +92,16 @@ After consideration of the [charter assessment criteria](#charter-assessment-cri
92
92
93
93
#### 3.2.1 Technical Strategy Team decision to initiate charter refinement {#cr-acceptance}
94
94
95
-
If the Technical Strategy Team decides to initiate charter refinment, it follows these steps:
95
+
If the Technical Strategy Team decides to initiate charter refinement, it follows these steps:
96
96
97
97
Select a Chartering Facilitator
98
-
: The Technical Strategy Team Lead selects a [Chartering Facilitator](#chartering-facilitator) and records that appointment in the [pipeline](#pipeline).
98
+
: For the rechartering of existing groups, the Team Contact is selected by default as Chartering Facilitator and should assign the github issue to themselves. Otherwise, the [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) and/or [Project & Process Team Lead](https://www.w3.org/staff/project/) select a [Chartering Facilitator](#chartering-facilitator) and records that appointment in the [pipeline](#pipeline) by assigning github issues.
99
99
100
100
Request announcement of initiation of charter refinement
101
-
: The [Chartering Facilitator](#chartering-facilitator) then sends a request to the W3C Communications Team to [announce the initiation of charter refinement](adv-notice.md); that document lists requirements for the announcement. In practice, if the announcement would precede the call for AC review by only a short delay, we skip the refinement phase.
101
+
: The [Chartering Facilitator](#chartering-facilitator) then sends a request to the W3C Communications Team to [announce the initiation of charter refinement](adv-notice.md), copying the Technical Strategy Team Lead](https://www.w3.org/staff/strat/) and/or [Project & Process Team Lead](https://www.w3.org/staff/project/); that document lists requirements for the announcement. In practice, if the announcement would precede the call for AC review by only a short delay, we skip the refinement phase.
102
102
103
103
Record start of refinement
104
-
: Once refinement has been announced, the Technical Strategy Team Lead records the initiation of charter refinement in the [pipeline](#pipeline) issue.
104
+
: Once refinement has been announced, the Technical Strategy Team Lead](https://www.w3.org/staff/strat/) or [Project & Process Team Lead](https://www.w3.org/staff/project/) records the initiation of charter refinement in the [pipeline](#pipeline) issue.
105
105
106
106
Any Formal Objection to a Team Decision to initiate charter refinement is not considered registered until the close of any Advisory Committee Review of that charter, and is registered against that W3C Decision.
0 commit comments