Skip to content

Commit

Permalink
Update links and markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
vivienlacourba committed Jan 9, 2025
1 parent 24ebcfc commit ff5f5f3
Showing 1 changed file with 25 additions and 30 deletions.
55 changes: 25 additions & 30 deletions process/adv-notice.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,28 +3,27 @@ title: How to send advance notice of work to the Advisory Committee
toc: yes
---

This document describes the [Strategy Team](https://www.w3.org/staff/strat/)'s [implementation](#policy) of the [Process Document requirements](/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.
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.

## Sending advance notice to the Advisory Committee {#policy}

Who/Where
: The <a href="https://www.w3.org/staff/strat/">Strategy team</a> determines when
: 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 <a href="https://www.w3.org/staff/comm/">W3C Communications
Team</a> to [email protected] and then forwarded to: [email protected].

Unless an advance notice strongly requires
Member-only confidentiality (which should be rare), we also inform the
public
via <a href="https://lists.w3.org/Archives/Public/public-new-work/">[email protected]</a> (
see <a href="https://lists.w3.org/Archives/Public/public-new-work/2022Mar/0012.html">example</a>) and <a href="https://www.ietf.org/mailman/listinfo/new-work">[email protected]</a>. This
the [W3C Communications Team](https://www.w3.org/staff/comm/) to [email protected]
and then forwarded to [email protected].

Unless an advance notice strongly requires Member-only confidentiality
(which should be rare), we also inform the public
via [public[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 [new-work@ietf.org](https://www.ietf.org/mailman/listinfo/new-work). This
is done by the W3C Communications Team.


When
: Specialists, in conjunction with the Strategy Lead, make this
decision based on early assessment of the factors available in the
"<a href='https://github.com/w3c/strategy/blob/master/3.Evaluation.md'>Evaluation</a>" section of the Funnel,
"[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
Expand All @@ -35,16 +34,14 @@ sent for charter review, but an indication that the Team is seriously
evaluating possible work, and seeks wider feedback.

How/What
: There is
a <a href="https://www.w3.org/new-doc-from-template?location=%2FTeam%2F&amp;template=%2Fafs%2Fw3.org%2Fpub%2FWWW%2FTeam%2FTemplates%2Fadv-charter.html&amp;submit=Continue...">template
for advance notice</a>. Please look for recent examples in
the <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/">w3c-ac-members
archive</a>.
: There is a [template](https://www.w3.org/new-doc-from-template?location=%2FTeam%2F&amp;template=%2Fafs%2Fw3.org%2Fpub%2FWWW%2FTeam%2FTemplates%2Fadv-charter.html&amp;submit=Continue...)
for advance notice</a>. Please look for recent examples in the
[w3c-ac-members archive](https://lists.w3.org/Archives/Member/w3c-ac-members/).

The advance notice announcement to the Membership MUST include this
information:

- A summary of the intended work
- 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.
Expand All @@ -53,25 +50,23 @@ information:
The advance notice announcement to the Membership SHOULD include this
information:

- Expectations about when a formal Advisory Commitee Review might begin.</li>
- Expectations about when a formal Advisory Commitee Review might begin.

The advance notice announcement to the Membership MAY include this
information:

- 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.
- 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.

## Background for this document {#bg}

The [Process Document requirements](/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).
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."
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](http://www.w3.org/2002/05/rec-tips), in
particular:
These ideas are further discussed in [Tips for Getting to Recommendation Faster](http://www.w3.org/2002/05/rec-tips),
in particular:

{% include quote.html content="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."%}
> 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.

0 comments on commit ff5f5f3

Please sign in to comment.