W3C home > Mailing lists > Public > public-w3process@w3.org > December 2013

Re: w3process-ISSUE-73 (PubRules-Evolution): Pub Rules' rules, maintenance, evolution, etc. should be transparent and Public [Publication Rules (aka PubRules)]

From: Ian Jacobs <ij@w3.org>
Date: Fri, 6 Dec 2013 09:37:23 -0600
Message-Id: <A39060DA-C1A8-4F80-AFB9-1B83EEF3E7F0@w3.org>
To: Revising W3C Process Community Group <public-w3process@w3.org>

On Dec 6, 2013, at 9:33 AM, "Revising W3C Process Community Group Issue Tracker" <sysbot+tracker@w3.org> wrote:

> w3process-ISSUE-73 (PubRules-Evolution): Pub Rules' rules, maintenance, evolution, etc. should be transparent and Public [Publication Rules (aka PubRules)]
> 
> http://www.w3.org/community/w3process/track/issues/73
> 
> Raised by: Arthur Barstow
> On product: Publication Rules (aka PubRules)
> 
> The enforcement of the so-called TR "Pub Rules" can be a process bottleneck in that "surprises happen" that block TR publications (f.ex. see Issue-71).
> 
> In <http://lists.w3.org/Archives/Public/public-w3process/2013Dec/0034.html>, Ian indicates "Responsibility for pubrules lies with the comm team". From my perspective, that effectively means PubRules' rules, maintenance, evolution, etc. is neither transparent nor public. To help prevent TR publication blockages because of PubRules, PubRules' evolution should be transparent and Public.

Hi Art,

+1 to a public tracker for pubrules issues.

Ian

--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                                          +1 718 260 9447
Received on Friday, 6 December 2013 15:37:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:09 UTC