Re: CfC: create a public list to announce new publications; deadline Oct 15

I support the idea, but a few more things should be made clear.

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.

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

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



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

I suggest it be named public-review (that is what it is for).  “This list is solely for the announcement of public reviews; discussion happens on the public mailing lists of the concerned groups.”  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.


On Oct 8, 2014, at 13:27 , chaals@yandex-team.ru wrote:

> 08.10.2014, 16:41, "Jeff Jaffe" <jeff@w3.org>:
>> On 10/8/2014 7:09 AM, Arthur Barstow wrote:
>>>  In the spirit of facilitating and increasing the likelihood of early
>>>  and wide document reviews, a number of people in thread [1] voiced
>>>  support for creating a Public list the Publications team would use to
>>>  announce publications of FPWDs, LCWDs, 2014-preCRs and CRs. This is a
>>>  Call for Consensus (CfC) to create such a list and for the
>>>  Publications team to use it when these types of documents are published.
>>> 
>>>  If anyone has any comments or concerns about this CfC, please reply by
>>>  Oct 15.
>> 
>> I support this proposal.  We may need more [2], but this would be a good
>> start.
> 
> I tentatively support the proposal. When a Working Draft is published for review beyond the Working Group, with a specific pointer to what should be reviewed, I think it should go to such a list.
> 
> Assuming that review can be done when a spec is mostly baked is a *problem*. Modern rapid development means that by that time the cost of changes is quite high. The time for review is when a feature is introduced.
> IMHO.
> 
> (CG chair nitpicking:
> This group doesn't tell W3C what to do. It makes requests.
> 
> Sometimes the AB works *in* this group - specifically in the context of its Process Task Force, which is currently chaired by Steve Zilles. While most people probably don't care about the various differences, it is probably helpful to try and keep them straight and clear.)
> 
> cheers
> 
>>>  Assuming this CfC `passes`, a secondary issue is the name of the list.
>>>  I am indifferent and offer these possibilities:
>>>  public-{pubs,publications}; other suggestions are welcome and encouraged.
> 
> I couldn't care less what it's called.
> 
>>>  -Thanks, AB
>>> 
>>>  [1]
>>>  <http://lists.w3.org/Archives/Public/public-w3process/2014Oct/0000.html>
>> 
>> [2] http://www.w3.org/community/w3process/track/issues/144
> 
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com
> 

David Singer
Manager, Software Standards, Apple Inc.

Received on Wednesday, 8 October 2014 21:29:20 UTC