Re: CfC: Set up automatic WD publication for the WG's deliverables

I'll set things up.

Just for clarity, for the Presentation API and Remote Playback API, the 
publication status won't be "Working Draft" but "Candidate 
Recommendation Draft", since both of these documents have already been 
published as Candidate Recommendation Snapshots.

As mentioned below, publication of new Candidate Recommendation 
Snapshots for these specifications still requires a WG decision, see the 
recommendation track in the Process document for details [1].

Francois.

[1] https://www.w3.org/2021/Process-20211102/#rec-track

------ Original message ------
From: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
To: "public-secondscreen@w3.org" <public-secondscreen@w3.org>; "Francois 
Daoust" <fd@w3.org>
Cc: "Louay Bassbouss" <louay.bassbouss@fokus.fraunhofer.de>
Date: 14/04/2022 14:40:27

>Hi All, Francois,
>
>This CfC passed with explicit support (thanks Rod and Mike!).
>
>Francois - please feel free to set up the CI integration at your 
>leisure to enable automatic WD publication for the WG’s deliverables.
>
>Thanks,
>
>-Anssi
>
>>On 5. Apr 2022, at 10.24, Kostiainen, Anssi 
>><anssi.kostiainen@intel.com> wrote:
>>
>>Hi Second Screen WG,
>>
>>This is a Call for Consensus to set up automatic Working Draft (WD) 
>>publication for the Working Group’s deliverables [1], currently:
>>
>>Presentation API
>>Remote Playback API
>>Open Screen Protocol
>>Multi-Screen Window Placement (subject to successful First Public 
>>Working Draft publication)
>>
>>In scope of this CfC is also any deliverable that may be added to the 
>>WG in the future.
>>
>>In practice this means that when an Editor’s Draft is updated a new 
>>Working Draft is automatically published at 
>>https://w3.org/TR/{shortname}
>>
>>This publication practice adopted by many WGs ensures a spec hosted at 
>>"TR space” (that is indexed high by many search engines) reflects the 
>>latest version. Publishing a spec on any other maturity level [2] 
>>still requires a WG decision (e.g. via a CfC) and is a manual process.
>>
>>In our experience, this automation helps editors by automating the 
>>publication task, increases the editorial quality of the publications 
>>by means of an automatic validation step, and makes it easier for the 
>>consumers of the specs to find the latest specification version.
>>
>>If you have any comments, questions or concerns with this proposal, 
>>please respond by 13 Apr 2022.
>>
>>Thanks,
>>
>>-Anssi (Second Screen WG/CG co-chair)
>>
>>
>>[1] 
>>https://www.w3.org/2022/03/charter-secondscreen-wg.html#deliverables
>>[2] https://www.w3.org/2021/Process-20211102/#maturity-levels
>

Received on Friday, 15 April 2022 09:28:36 UTC