Modified charter howto for charter refinement

process/adv-notice.md

@@ -1,72 +1,47 @@
 ---
-title: How to send advance notice of work to the Advisory Committee
+title: Announcing the start of Charter Refinement
 toc: yes
 ---
 
-This document describes the [Strategy Team](https://www.w3.org/staff/strat/)'s [implementation](#policy) of the [Process Document requirements](https://www.w3.org/policies/process/#WGCharterDevelopment) related to advance notice to the Advisory Committee of charters in development. See the [background](#bg) for the advance notice policy and this document.
+The W3C Process defines a [charter refinement phase](https://www.w3.org/policies/process/drafts/#charter-initiation) to help ensure that draft charters are mission-aligned, reflect community input and consensus, and have been well-socialized and widely reviewed *before* formal review by the Advisory Committee. 
 
-## Sending advance notice to the Advisory Committee {#policy}
+This document describes how the W3C Communications Team announces the
+start of charter refinement with a *charter review notice*. For
+information about when the Strategy Team may request that the Comm
+Team send this announcement and activities following this
+announcement, see [How to create a Working Group or Interest
+Group](charter.md).
 
-Who/Where
-: The [Strategy Team](https://www.w3.org/staff/strat/) determines when
-to inform the AC of work-in-progress. These announcements are sent by
-the [W3C Communications Team](https://www.w3.org/staff/comm/) to [email protected]
-and then forwarded to [email protected].
+# Drafting the charter review notice
 
-  Unless an advance notice strongly requires Member-only confidentiality
-(which should be rare), we also inform the public
-via [[email protected]](https://lists.w3.org/Archives/Public/public-new-work/)
-(see [example](https://lists.w3.org/Archives/Public/public-new-work/2022Mar/0012.html))
-and [[email protected]](https://www.ietf.org/mailman/listinfo/new-work). This
-is done by the W3C Communications Team.
+Per [section 4.1 of the Process Document](https://www.w3.org/policies/process/drafts/#charter-initiation) the charter review notice must include the following:
 
-When
-: Specialists, in conjunction with the Strategy Lead, make this
-decision based on early assessment of the factors available in the
-"[Evaluation](https://github.com/w3c/strategy/blob/master/3.Evaluation.md)" section of the Funnel,
-as well as considering when it is useful to encourage broader input to
-discussion. In the Process-required notice to the AC, the Strategy
-team will give an early status report on the work and likely timeline
-for further progress (from information captured in the Funnel).
+* A short summary of the proposal.
+* The location of the charter draft, which must be public.
+* How to participate in the discussion of this charter draft and where to file issues.
+* The expected duration of the charter refinement phase, which must not be less than 28 days, and should not be more than 6 months.
+* Who the Chartering Facilitator is.
 
-  Advance notice is not an indication that work *will* necessarily be
-sent for charter review, but an indication that the Team is seriously
-evaluating possible work, and seeks wider feedback.
+In addition, the Team *may* include its own perspectives about the charter in the review notice.
 
-How/What
-: There is a [template](https://www.w3.org/new-doc-from-template?location=%2FTeam%2F&template=%2Fafs%2Fw3.org%2Fpub%2FWWW%2FTeam%2FTemplates%2Fadv-charter.html&submit=Continue...)
-for advance notice. Please look for recent examples in the
-[w3c-ac-members archive](https://lists.w3.org/Archives/Member/w3c-ac-members/).
+Please use the [advance notice template](https://www.w3.org/new-doc-from-template?location=%2FTeam%2F&template=%2Fafs%2Fw3.org%2Fpub%2FWWW%2FTeam%2FTemplates%2Fcharter-review-notice.html&submit=Continue...) to create an initial draft.
 
-  The advance notice announcement to the Membership MUST include this
-information:
+# Sending the charter review notice
 
-  - A summary of the intended work.
-  - A statement welcoming the Members to use w3c-ac-forum for general expressions of interest and support.
-  - A request that Members send substantive comments and engage on substantive discussion on a different mailing list or github repository (i.e., **other than w3c-ac-forum**).
-  - If applicable, a statement that the archive of this second list is Member-visible.
-  - Contact information if people have questions; generally these will be the names of one or more people on the Team.
+The Communications Team sends the charter review notice to:
 
-  The advance notice announcement to the Membership SHOULD include this
-information:
+* [email protected] (then forwards it to [email protected]).
+* The affected group (in the case of a rechartering).
 
-  - Expectations about when a formal Advisory Commitee Review might begin.
+In addition, unless this notice requires Member-only confidentiality
+(which should be rare), the Communications Team also sends the notice
+to:
 
-  The advance notice announcement to the Membership MAY include this
-information:
+* [email protected]
+* [email protected]
 
-  - Pointers to draft materials. In other words, the announcement is not
-required to include a draft charter, but if one is available, please include it.
-  - Information about other mailing lists for comments, as the situation requires.
+# After the notice has been sent
 
-## Background for this document {#bg}
+[Section 4.2 of the Process Document](https://www.w3.org/policies/process/drafts/#charter-development) describes activities during the refinement phase, and in particular the role of the Charter Facilitator to seek consensus and how and when any Formal Objections are handled.
 
-The [Process Document requirements](https://www.w3.org/policies/process/#WGCharterDevelopment) for advance notice were introduced in response to requests from Members to be more in the loop earlier for work in development. These requirements were added to provide additional transparency to some work carried out (in general) by the Team, to encourage Members to show support for work in development early (on w3c-ac-forum), and to enable those interested in shaping a charter to participate on a separate list (so as not to flood w3c-ac-forum).
-
-Hence the sentence in the Process Document:
-> Advisory Committee representatives MAY provide feedback on the Advisory Committee discussion list or via other designated channels.
-
-These ideas are further discussed in [Tips for Getting to Recommendation Faster](../standards-track/rec-tips.md),
-in particular:
-
-> When a Charter is proposed to the Advisory Committee, garner support from fellow W3C Members on w3c-ac-forum. When there is substantial support for new work among the Members, the Team may create a special mailing list for discussion among Members and Team about Group charter development. Start discussions with proposals, calendars, statements of expected resource commitments, and other such signals.
+**Note**: Advance notice is not an indication that work *will* necessarily progress to formal Advisory Committee review.