- From: <timeless@gmail.com>
- Date: Wed, 08 Oct 2014 17:35:52 -0400
- To: public-w3process <public-w3process@w3.org>
David wrote: > I support the idea, but a few more things should be made clear. +1 > A) Use this list when this is a good time for people outside the mailing list to do a review; the document is readable, and so on. Yes, you can ask for review whenever and as often as you like, but beware, people have a limited energy for reviewing the same document multiple times. Choose wisely. +1 > B) You MUST indicate a deadline for the review of the document, and the document MUST be stable (at that URL) while people are trying to review it. Sure you can keep revising at a different URL, but don’t force people to critique a moving target (but if there is a bleeding edge that is not the document, you MUST tell them where to find it as well). +1 > C) It’s fine if some sections are marked as TBD or half-baked, and so on: just please set reviewer’s expectations correctly. (An early review might be to ask for the overall architecture, data-flows, and approach, with details of the APIs or markup very provisional, for example). Sure > I would still like it if the list of documents open for review were kept on a page somewhere (and I bet it’s not hard). Yep > I suggest it be named public-review (that is what it is for). Possibly public-review-announce But either works for me. > “This list is solely for the announcement of public reviews; discussion happens on the public mailing lists of the concerned groups.” Yes > I suggest therefore that it’s something chairs and editors can have something sent to, reply-to is always set, and other attempts to send to the list will fail. This is not a place for discussion. Yes
Received on Wednesday, 8 October 2014 21:36:20 UTC