Skip to content

Commit

Permalink
Contributions from @r12a
Browse files Browse the repository at this point in the history
  • Loading branch information
@plehegar
plehegar committed Jul 1, 2021
1 parent b47e64d commit 3a240e1
Showing 1 changed file with 47 additions and 42 deletions.
89 changes: 47 additions & 42 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -54,62 +54,67 @@ <h2>When should wide review be requested?</h2>
</ul>
</section>



<section id="who_to_ask_for_review">
<h2>Who to ask for wide review?</h2>

<p>The objective is to ensure that the entire set of stakeholders of the Web
community, including the general public, have had adequate notice of the
progress of the Working Group and were genuinely able to perform reviews of and
provide comments on the specification. When considering <a
href='https://www.w3.org/Guide/transitions'>requests to advance the maturity
level of document</a>, the Director will consider who has been explicitly
offered a reasonable opportunity to review the document.</p>

<p>In order to include other stakeholders including Web developers, technology
providers and implementers not active in the Working Group, external groups and
standards organizations working on related areas, etc. you must:</p>
<p>The objective is to ensure that the entire set of stakeholders of the Web
community, including the general public, have adequate notice of the progress
of the Working Group and are able to actually perform reviews of and provide
comments on the specification. When considering <a
href="https://www.w3.org/Guide/transitions">requests to advance the maturity
level of the document</a>, the Director will consider who has been explicitly
offered a reasonable opportunity to review the document.</p>

<p>You must publish an updated technical report, with the Status of the Document
indicating clearly that you're looking for <em>wide review</em>, before inviting
review from other stakeholders. Our <a
href='https://github.com/w3c/transition-notifier/blob/main/notify.js'>tooling</a>
monitors publications and propagates notifications to <a
href="mailto:public-review-announce@w3.org">public-review-announce@w3.org</a>
automatically (for example, <a
href='https://lists.w3.org/Archives/Public/public-review-announce/2021Jun/0008.html'>Candidate
Recommendation Snapshot: Payment Request API (Call for Wide Review)</a>).</p>

<p>You should then reach out to:</p>

<ul>
<li>Publish an updated technical report, with the Status of the Document indicating clearly
that you're looking for <em>wide review</em>.
<p>Our <a
href='https://github.com/w3c/transition-notifier/blob/main/notify.js'>tooling</a>
monitors publications and propagates to <a
<li>the groups listed in the WG's charter, especially those who manage
dependencies.</li>
<li>the groups jointly responsible for a particular document (if any).</li>
<li>the <a href="#how_to_get_horizontal_review">horizontal groups</a>. If it
appears that one of those is not relevant (even if not listed in your charter),
talk to them informally to confirm that. <em>Note that sending an email to the
public-review-announce list alone is not sufficient to trigger horizontal
reviews. You will still need to formally request review from the Horizontal
Groups, as described below</em></li>
<li>the general public, including Web developers, technology providers and
implementers, application developers, etc. Consider:
<ul>
<li>sending a dedicated announcement to <a
href="mailto:public-review-announce@w3.org">public-review-announce@w3.org</a>
automatically (for example, <a
href='https://lists.w3.org/Archives/Public/public-review-announce/2021Jun/0008.html'>Candidate
Recommendation Snapshot: Payment Request API (Call for Wide Review)</a>).</p>
</li>
<li>Inform, and request review from, the Groups listed in the WG's charter, especially those who
manage dependencies.</li>
<li>Inform, and request review from, to the Groups jointly responsible for a particular document (if any).</li>
<li><a href="#how_to_get_horizontal_review">Request reviews</a> from the
<a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">horizontal groups</a></li>
<li>Actively inform the general public. Beyond the publication, you do so by:
<ol>
<li>Sending a dedicated announcement to <a
href="mailto:public-review-announce@w3.org">public-review-announce@w3.org</a>
if needed (in case the default notice sent to that list is
not enough).
</li>
<li>Considering using blog posts, social media, or other ways
of alerting the public to your document and requesting feedback.</li>
</ul>
if needed (in case the default notice sent to that list is not enough).</li>
<li>using blog posts, social media, or other ways of alerting the public to
your document and requesting feedback.</li>
</ul>
</li>

<p>In addition, you should consider contacting other groups, at your
discretion, even if not in the WG charter, including other W3C groups, external
organizations and SSOs, implementers, application developers, etc.</p>
<li>other groups, at your discretion, even if not in the WG charter, such as
other W3C groups, external organizations and SSOs working on related areas,
etc.</li>

</ul>

<p><strong>Tip:</strong> consider tracking your wide review progress using a
GitHub issue, such as <a href="https://github.com/w3c/sensors/issues/299">issue
#299 of th Sensors API</a>. You can then simply point the Director to the issue.</p>
#299 of the Sensors API</a>. You can then simply point the Director to the
issue.</p>


<p>The reviews provided by the <a
href="https://www.w3.org/Guide/process/charter.html#horizontal-review">horizontal
groups</a>, a subset of a full wide review, do receive special attention and
much of the rest of this document focuses on how and when to conduct horizontal reviews.</p>
much of the rest of this document focuses on how and when to conduct horizontal
reviews.</p>

</section>

Expand Down

0 comments on commit 3a240e1

Please sign in to comment.