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

CfC: Set up automatic WD publication of Wake Lock API based on ED changes : respond by 28 January

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Wed, 14 Jan 2015 07:36:39 -0500
To: W3C Device APIs WG <public-device-apis@w3.org>
Message-Id: <A6CD57D2-00B7-480D-8E94-0A4319D4517C@fjhirsch.com>
This is a call for consensus (CfC) to arrange for automatic Working Draft publications (WD) of the Wake Lock API based on Editor draft updates. This means that every time the editor updates the draft and requests an update via an HTTP POST the change would be reflected automatically in a WD publication (without voting or manual processing etc). 

I believe this still allows the editor(s) to complete a variety of edits and review and check the changes (e.g. validation/link checks etc) before triggering the WD update, but will require diligence on the part of the editor(s) to make sure WD publications are correct.

We have a  separate CfC to publish a FPWD of the Wake Lock API - that CfC is completing 19 January -  please respond to that CfC as well as this one

(see http://lists.w3.org/Archives/Public/public-device-apis/2014Dec/0015.html )

Once we have agreed to publish a FPWD then it would be good to agree to this CfC to make sure the details of WD publication are in place before publishing. 

This CfC proposes using "Setup automatic WD from http://www.w3.org/2014/08/pubworkflow.html for Wake Lock API WD updates based on editor draft updates.

To be clear, this CfC only applies to the Wake Lock API; no change to previous publication handling.

Please respond within two weeks, by 28 January 2015. An explicit expression of support (+1) or concern is preferred. Silence will be assumed to be consent.


regards, Frederick

Frederick Hirsch, Nokia
Chair W3C Device APIs WG
Received on Wednesday, 14 January 2015 12:37:17 UTC

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