RE: w3process-ISSUE-126 (autoWDpublish): Automatic WD publishing tool may change the W3C center of gravity around WGs [Process Document]

> If an editor 'goes rogue' and starts publishing what appear to be WG WDs without the WG agreement, I rather think their life as an editor may be short,

+1.  I think Chairs have the tools they need to handle this situation. Plus with the one-click publish tool, an editor can't hold the chair hostage by saying "the publication process is so complex, it will take you forever to find a replacement if you fire me" :-)

-----Original Message-----
From: David (Standards) Singer [mailto:singer@apple.com] 
Sent: Wednesday, September 10, 2014 12:27 PM
To: Revising W3C Process Community Group
Subject: Re: w3process-ISSUE-126 (autoWDpublish): Automatic WD publishing tool may change the W3C center of gravity around WGs [Process Document]


On Sep 10, 2014, at 2:47 , Revising W3C Process Community Group Issue Tracker <sysbot+tracker@w3.org> wrote:

> During the CSS WG ftf 10-sep-2014, plh presented the new proposed tool allowing an editor to publish a WD with one-click. A side effect of that tool is that it allows to turn the editor into a decider while the current situation always sets the WG as the decider to publish. It basically allows to "officialize" Editor's Draft into the Process as WDs, the editor potentially having the ability granted by WG to publish when he wants, as often he wants.

I rather assume that we are under the existing system, that the editor works at the behest of the WG, making edits, publishing, and coordinating as authorized.  If an editor 'goes rogue' and starts publishing what appear to be WG WDs without the WG agreement, I rather think their life as an editor may be short, or due for a re-programming, no?

Making publication physically easy does not mean it is free of moral encumbrance.

David Singer
Manager, Software Standards, Apple Inc.

Received on Wednesday, 10 September 2014 19:45:49 UTC