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
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ Community Groups interested in transitioning to a Working Group are encouraged t
90
90
91
91
After consideration of the [charter assessment criteria](#charter-assessment-criteria) and a determination that the charter is well-formed (per the template and per Process section "[content of a charter](https://www.w3.org/policies/process/#WGCharter)"), the Technical Strategy Team Lead decides whether to initiate charter refinement.
92
92
93
-
#### 3.2.1 Technical Strategy Team decision to initiate charter refinement
93
+
#### 3.2.1 Technical Strategy Team decision to initiate charter refinement {#cr-acceptance}
94
94
95
95
If the Technical Strategy Team decides to initiate charter refinment, it follows these steps:
96
96
@@ -105,7 +105,7 @@ Record start of refinement
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.
107
107
108
-
#### 3.2.2 Technical Strategy Team decision not to initiate charter refinement
108
+
#### 3.2.2 Technical Strategy Team decision not to initiate charter refinement {#cr-rejection}
109
109
110
110
If no Advisory Committee representative formally requested that the Technical Strategy Team initiate charter refinement, then no further action is required of the Technical Strategy Team.
111
111
@@ -115,7 +115,7 @@ This rejection is a [Team Decision](https://www.w3.org/policies/process/#team-de
115
115
116
116
> **Note**: We do not expect to include operational details for handling these Formal Objections until we have gained experience.
117
117
118
-
### 3.3 Activities during refinement
118
+
### 3.3 Activities during refinement {#during-refinement}
119
119
120
120
The Chartering Facilitator is responsible for seeking community consensus among those participating in the refinement process and making decisions reflecting that consensus. The Chartering Facilitator follows these steps during refinement:
121
121
@@ -196,6 +196,8 @@ In this section we describe the operational aspects of extending or modifying th
196
196
197
197
The W3C Process describes the [charter extensions](https://www.w3.org/policies/process/#charter-extension) and when they may occur. No Advisory Committee review is required for short-term extensions.
198
198
199
+
Advisory Committee representatives may initiate an [Advisory Committee Appeal](ac-appeal.md) against a [Team decision](https://www.w3.org/policies/process/#charter-extension) regarding the extension of a Working Group or Interest Group charter.
200
+
199
201
The Technical Strategy Team expects a charter extension to be no more than 6 months. Otherwise the Group must [recharter](#recharter-request) or justification must be provided to explain the delay.
200
202
201
203
Short-term extensions cannot exceed a total of one year from the original charter end date.
0 commit comments