Tool to Assist with Calls for Specification Review

This tool is no longer recommended for use, as of November 2019.

Further guidance on document review.

This form is meant to help Chairs and Team contacts get Document Review via the list <public-review-announce@w3.org>.

Again, this tool (and the public-review-announce@w3.org mailing list) is no longer recommended for use, as of November 2019.

Generate Draft Email

Choose a Working Group or Interest Group

Spec title

Spec URI (stable or latest version)

Publication type

Feedback (email, URI, or text)

Comments due (YYYY-MM-DD)

What do you want people to focus on (optional)?

    (Push "Generate Draft Email" to update this text.)

FAQ

Tell me about public-review-announce@w3.org

Subscribers: W3C Chairs and W3C Staff are automatically subscribed; anyone else may subscribe
Read access: Public
Write access: Public

Am I required to use this list to get wide review?

No.

Does this list replace any of the lists described in the transition documentation?

No. References: Transitions for 2005 Process and Transistions for 2014 Process.

Does announcing a publication on this review list constitute wide review?

No. The announcement is merely an invitation to review. The W3C Process expects actual reviews to happen.

Can we use this list to seek review for any type of publication?

Yes, for Working, Interest, Community, and Business Groups. The publication status (e.g,. FPWD or CR) will likely affect what review you seek, and where possible you should be specific about what feedback you want.

Will the staff send emails to this list automatically?

That is not currently the plan given that groups have expressed that they wish to send custom messages.

Notes

A complete tool will actually post the email to the list.
The form could be a lot more intelligent, e.g., getting the title of the document given the URI, getting the email address for comments given the identified group, the list of groups could be limited to those for which the logged in individual is team contact or chair. This is just a demo.
More than one group may be responsible for a specification.
I don't think we should constrain groups to point reviewers only at unchanging drafts. Each group should make a choice.
We have a TR page view of review opportunities. Today it includes LC2005, CR2014, and PR.

Ian Jacobs. Comments or questions? <public-w3process@w3.org>