W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2015

Re: CfC to auto-update ED in TR Space (was: Progressing Wake Lock API to W3C FPWD?)

From: Arthur Barstow <art.barstow@gmail.com>
Date: Wed, 07 Jan 2015 07:49:37 -0500
Message-ID: <54AD2B61.1000203@gmail.com>
To: w3c@fjhirsch.com, Marcos Caceres <marcos@marcosc.com>
CC: W3C Device APIs WG <public-device-apis@w3.org>
On 1/6/15 8:59 AM, w3c@fjhirsch.com wrote:
> I took a look in the WebApps mail archive and did not see a CfC for managing the editors draft, but may have missed it.  Ive ccd Art in case he has a link.
>> FROM: Marcos Caceres <marcos@marcosc.com>
>> I can't remember if we ran a CFC to do this or not in this group (I think we did one in WebApps and no objections were raised). If not, we should start one ASAP.

Since (plain) WD publications don't (strictly speaking) require 
recording `consensus`, WebApps does not use a CfC for those 
publications. Instead, before such a publication is done, we expect 
someone (f.ex. an Editor, Chair, Staff) to issue a `heads up` (known as 
a PublicServiceAnnoucement f.ex. [PSA]) about the intent to publish a 
new WD.

Mapping this work mode to the context of [Pub-Workflow], if an Editor 
wants to get a spec on the auto-TR-update track, it seems like that bit 
of info would be included in their PSA to publish a new WD (and that an 
explicit CfC is not needed).


[Pub-Workflow] <http://www.w3.org/2014/08/pubworkflow.html>
Received on Wednesday, 7 January 2015 12:50:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:15 UTC