You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentreview/index.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ You should then inform, and request reviews from:
35
35
* the groups listed in the WG's charter, especially those who manage
36
36
dependencies.
37
37
* the groups jointly responsible for a particular document (if any).
38
-
* the [horizontal groups](../process/horizontal-groups.md) using the [method described below](#how_to_get_horizontal_review). *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*
38
+
* the [horizontal groups](../process/horizontal-groups.md) using the [method described below](#how-to-get-horizontal-review). *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*
39
39
* the general public, including Web developers, technology providers and implementers, application developers, etc. Consider:
40
40
* sending a dedicated announcement to [[email protected]](mailto:[email protected]) if needed (in case the default notice sent to that list is not enough).
41
41
* using blog posts, social media, or other ways of alerting the public to your document and requesting feedback.
@@ -74,11 +74,11 @@ The meaning of "Long enough" depends on how many changes there are, how clearly
74
74
<dt>Accessibility</dt>
75
75
<dd>
76
76
<spanclass="step">Work through <arel="nofollow"class="external text"href="https://w3c.github.io/apa/fast/checklist.html">this questionnaire</a></span> then
77
-
<spanclass="step"><arel="nofollow"class="external text"href="https://github.com/w3c/a11y-request/issues/new/choose">request a review via GitHub</a> from <arel="nofollow"class="external text"href="https://www.w3.org/WAI/APA/">APA</a></span>
77
+
<spanclass="step"><arel="nofollow"class="external text"href="https://github.com/w3c/a11y-request/issues/new/choose">request a review via GitHub</a> from <arel="nofollow"class="external text"href="https://www.w3.org/WAI/about/groups/apawg/">APA</a></span>
<ul><li> <arel="nofollow"class="external text"href="https://w3c.github.io/apa/fast/checklist.html">Framework for Accessibility in the Specification of Technologies Checklist; APA WG</a></li>
@@ -110,7 +110,7 @@ The meaning of "Long enough" depends on how many changes there are, how clearly
110
110
<details>
111
111
<summary>Show useful links</summary>
112
112
<ul><li>groups
113
-
<ul><li><arel="nofollow"class="external text"href="https://www.w3.org/International/">Internationalization Working Group</a>; <arel="nofollow"class="external text"href="https://lists.w3.org/Archives/Public/www-international/">www-international</a> Reviews by Internationalization generally also involve the <arel="nofollow"class="external text"href="https://www.w3.org/International/ig/">Interest Group</a>, but are arranged through the WG.</li></ul></li>
113
+
<ul><li><arel="nofollow"class="external text"href="https://www.w3.org/International/">Internationalization Working Group</a>; <arel="nofollow"class="external text"href="https://lists.w3.org/Archives/Public/www-international/">www-international</a> Reviews by Internationalization generally also involve the <arel="nofollow"class="external text"href="https://www.w3.org/International/i18n-activity/i18n-ig/">Interest Group</a>, but are arranged through the WG.</li></ul></li>
114
114
<li>links
115
115
<ul><li><arel="nofollow"class="external text"href="https://www.w3.org/International/review-request">Request a review</a></li>
@@ -123,12 +123,12 @@ The meaning of "Long enough" depends on how many changes there are, how clearly
123
123
<dt>Privacy</dt>
124
124
<dd>
125
125
<spanclass="step">Write a "Privacy Considerations" section for your document, taking into account the <arel="nofollow"class="external text"href="https://www.w3.org/TR/security-privacy-questionnaire/">Self-Review Questionnaire: Security and Privacy</a>, <arel="nofollow"class="external text"href="https://www.w3.org/TR/fingerprinting-guidance/">Mitigating Browser Fingerprinting in Web Specifications</a>, and <arel="nofollow"class="external text"href="https://www.rfc-editor.org/rfc/rfc6973.html">RFC6973</a></span> then
126
-
<spanclass="step"><arel="nofollow"class="external text"href="https://github.com/w3cping/privacy-request/issues/new/choose">request a review via GitHub</a> from the <arel="nofollow"class="external text"href="https://www.w3.org/Privacy/">Privacy Interest Group</a></span>.
126
+
<spanclass="step"><arel="nofollow"class="external text"href="https://github.com/w3cping/privacy-request/issues/new/choose">request a review via GitHub</a> from the <arel="nofollow"class="external text"href="https://www.w3.org/groups/ig/privacy/">Privacy Interest Group</a></span>.
<li><arel="nofollow"class="external text"href="https://www.w3.org/TR/security-privacy-questionnaire/"><cite>Self-Review Questionnaire: Security and Privacy</cite>, published by the TAG and PING</a></li>
@@ -220,15 +220,15 @@ Is it possible to make too many requests for review?
220
220
221
221
## Common mistakes when making a transition request
222
222
223
-
1. If you make substantive changes, you'll need to do a wide review for those before you move forward to the [next maturity stage](../documentreview/#who_to_ask_for_review).
223
+
1. If you make substantive changes, you'll need to do a wide review for those before you move forward to the [next maturity stage](../documentreview/#who-to-ask-for-wide-review).
224
224
1. Never ever exclude some [horizontal groups](../process/horizontal-groups.md) from your review requests because you concluded it was irrelevant for them or they haven't responded to your last request.
225
225
226
226
Let them make the decision that something is irrelevant to their field of expertise instead. You're welcome to time out if you don't hear back, and request to move forward anyway.
227
227
1. Publish a Working Draft or a Candidate Recommendation Draft when asking for reviews.
228
228
It's better for a Group to miss the fact that you fixed an issue in your editor's draft than the Team missing the fact you made an unreviewed substantive change in your editor's draft.
229
229
1. Don't flag your issues with one of those <spanclass="tag">\*-needs-resolution</span> labels, and don't remove one which has been applied (you *can* close the issue though, if it is resolved).
230
230
231
-
Those are intended solely to be used by [horizontal groups](../process/horizontal-groups.md) to [bring special attention](../documentreview/#What_happens_to_unresolved_issues_marked_needs-resolution).
231
+
Those are intended solely to be used by [horizontal groups](../process/horizontal-groups.md) to [bring special attention](../documentreview/#what-happens-to-unresolved-issues-marked--needs-resolution).
232
232
1. Don't assume that the horizontal group will be able to schedule and complete a review within 2 weeks so that you can proceed to CR.
233
233
234
234
They may not even be able to find someone with availability to do the review in that time, and then they need a week or two to discuss their response after the review, and then they'll send you comments that may require you to make substantive changes.
0 commit comments