W3C home > Mailing lists > Public > public-webappsec@w3.org > November 2014

Re: [webappsec] New W3C process and Last Call

From: Wendy Seltzer <wseltzer@w3.org>
Date: Mon, 10 Nov 2014 20:40:58 -0500
Message-ID: <5461692A.1010202@w3.org>
To: Brad Hill <hillbrad@fb.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
On 11/10/2014 04:54 PM, Brad Hill wrote:
> The W3C has a new, more streamlined process for Recommendation Track documents:
> http://www.w3.org/2014/Process-20140801/#Reports
> There is no longer an explicit "Last Call" stage required.
> With my hat on as chair, I feel that Last Call is a useful phase of the process.  Our group works asynchronously, our features have impact on features defined by other WGs, and historically a Last Call announcement has been very fruitful for us in terms of receiving input from the broader community.  It is a signal to someone with limited time to devote to review that new features are not planned and things are approaching their final shape.
> What do other members (and especially editors think)?  Should we abandon the Last Call in WebAppSec, or maintain it informally as part of our group's culture?

Another question here is what process you want to use for existing drafts.

For anything in post-Last Call stage under the old process, the old
process continues to apply; for anything earlier, the group has a
choice, until re-chartering, when we'll be moved over to the new process
for all new work.

has the gory details.

In either case, we're working on ways to encourage Wide Review apart
from the formal step of "Last Call."


Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
Policy Counsel and Domain Lead, World Wide Web Consortium (W3C)
http://wendy.seltzer.org/        +1.617.863.0613 (mobile)
Received on Tuesday, 11 November 2014 01:41:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:42 UTC