8000 Fixed and/or in charter facilitator picks · w3c/guide@67a51e1 · GitHub
[go: up one dir, main page]

Skip to content

Commit 67a51e1

Browse files
committed
Fixed and/or in charter facilitator picks
1 parent 053690d commit 67a51e1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

process/charter.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The [Technical Strategy Team](https://www.w3.org/staff/strat/) and [Project &amp
3939
### 2.2 Chartering Facilitator
4040
{:#chartering-facilitator}
4141

42-
The [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) and the [Project &amp 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.
42+
The [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) or the [Project &amp 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.
4343

4444
**Note:** If the Team Leads cannot identify a Chartering Facilitator, there may be delays in advancing the charter through the process.
4545

@@ -95,7 +95,7 @@ After consideration of the [charter assessment criteria](#charter-assessment-cri
9595
If the Technical Strategy Team decides to initiate charter refinement, it follows these steps:
9696

9797
Select a Chartering Facilitator
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 [Project &amp 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.
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/) or [Project &amp 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.
9999

100100
Request announcement of initiation of charter refinement
101101
: 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 the [Project &amp 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.

0 commit comments

Comments
 (0)
0