diff --git a/process/charter.html b/process/charter.html index 26adf4a98..162dad8f4 100644 --- a/process/charter.html +++ b/process/charter.html @@ -178,13 +178,16 @@

3. Charter Creation

3.1 Horizontal Review

-

Once there is agreement on a draft charter, ideally among Team Contact(s), candidate chairs(s), relevant interest groups, and interested community members, seek review from the Strategy Team and horizontal reviewers by: -

  1. Opening a Chartering issue in the Strategy Repo,
  2. +

    Once there is agreement on a draft charter, ideally among Team Contact(s), candidate chairs(s), relevant interest groups, and interested community members, seek review from the Strategy Team and horizontal reviewers by:

    +
      +
    1. Moving/Copying the draft charter into the charter-drafts Repo, naming it using the convention [YYYY]/[shortname-name]-[group-type].html .
    2. +
    3. Opening a Chartering issue in the Strategy Repo,
    4. Adding a card for the issue to the Incubation Pipeline,
    5. Adding the Horizontal review requested label to the issue, and
    6. -
    7. Optionally, announce the new charter-in-progress to team-strategy and/or on a Strategy Team call.
    8. -

    +
  3. Creating an issue in w3c/AB-memberonly to alert the AB and our Members.
  4. +
  5. Optionally, announcing the new charter-in-progress to team-strategy and/or on a Strategy Team call.
  6. +

Horizontal reviewers will usually respond within two weeks, though it is wise to allow for additional time.

@@ -300,6 +303,7 @@

5.1 Organizing the Call for Review

  • A recommended review start date and duration (at least 28 days according to the process document)
  • A URI to the review of the proposed charter in the Strategy GitHub repository
  • The name of the Team-only mailing list for comments
  • +
  • All proposed charters must have a copy in w3c/charter-drafts and point there for GitHub issues.
  • @@ -595,6 +599,7 @@

    Revision History

  • 2015-09: Updates to Process Document section numbers and titles. Removed "Activities" and "Coordination Groups" which are no longer referenced in the 2015 Process Document.
  • 2016-02: Updated mostly to reflect that the Groups DB interfaces with IPP and that systeam creates new WGs/IGs; pointed to most recent sample announcement for Director's Decision and Call for Participation; updated workflows to match current practice; further removed or clarified that "Activities" are no longer in Process..
  • 2018-01: Took latest process into account
  • +
  • 2023-05: TiLT took over from W3M.