W3C home > Mailing lists > Public > public-webappsec@w3.org > March 2015

Re: CFC: All publications in WebAppSec to use new W3C publication process, was Re: CFC to push use new publishing process

From: Mike West <mkwst@google.com>
Date: Thu, 26 Mar 2015 06:03:47 +0100
Message-ID: <CAKXHy=dTHbQNop8V0CjuC2VQcnkLr33T76FSw6ZWEpmOgyqdaw@mail.gmail.com>
To: Brad Hill <hillbrad@gmail.com>
Cc: Marcos Caceres <marcos@marcosc.com>, Mounir Lamouri <mounir@lamouri.fr>, "public-webappsec@w3.org" <public-webappsec@w3.org>, Frederik Braun <fbraun@mozilla.com>, Wendy Seltzer <wseltzer@w3.org>, Daniel Veditz <dveditz@mozilla.com>, Devdatta Akhawe <dev.akhawe@gmail.com>
+1

--
Mike West <mkwst@google.com>, @mikewest

Google Germany GmbH, Dienerstrasse 12, 80331 München,
Germany, Registergericht und -nummer: Hamburg, HRB 86891, Sitz der
Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine Elizabeth
Flores
(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)

On Wed, Mar 25, 2015 at 9:06 PM, Brad Hill <hillbrad@gmail.com> wrote:

> +1, Thanks Marcos!
>
> On Wed, Mar 25, 2015 at 11:35 AM Marcos Caceres <marcos@marcosc.com>
> wrote:
>
>> (Sorry for what seems like a repeated CFC email... it's not, I promise...)
>>
>> Please note: you don't need to reply to this message unless you object or
>> need clarification. Silence is taken as support.
>>
>> I'm sending this as a new CFC because the W3C requires us to have a
>> stable URI to this message (plus it needs to be easy to find). Hence it's
>> quite important to have this email in the archive.
>>
>> This is a call for consensus to move all specification in the Web Apps
>> Sec group to use the new W3C publication process. This CFC ends on the 2nd
>> of April, 2015. The new process is one whereby specs that are WDs can be
>> automatically pushed to the /TR/ space without requiring CFC through this
>> mailing list.
>>
>> This message will then:
>>
>>  1. Allow Editors to get auto-publication tokens for all specs in this
>> group: see [0] for how to request a token from the W3C for your spec (you
>> can do that right now!).
>>  2. Actually be able to publish using Echidna [1] (the W3C's new system
>> that handles all this).
>>
>> If you want to learn how to use Echidna system with ReSpec + GitHub, see
>> [2] and [3]. It should work also with BikeShed specs. If you want help
>> getting set up, please email me privately and I will be happy to help you
>> (or point you to someone at the W3C who can help).
>>
>> [0] https://github.com/w3c/echidna/wiki/How-to-use-
>> Echidna-with-ReSpec-and-GitHub#the-token
>> [1] https://github.com/w3c/echidna
>> [2] https://github.com/w3c/echidna/wiki/How-to-use-
>> Echidna-with-ReSpec-and-GitHub
>> [3] https://lists.w3.org/Archives/Public/spec-prod/2015JanMar/0034.html
>>
>>
>>
Received on Thursday, 26 March 2015 05:04:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:11 UTC