W3C home > Mailing lists > Public > www-archive@w3.org > September 2010

HTML WG new timeline

From: Shelley Powers <shelleyp@burningbird.net>
Date: Wed, 08 Sep 2010 08:36:20 -0500
Message-ID: <4C879154.8050805@burningbird.net>
To: www-archive@w3.org, Maciej Stachowiak <mjs@apple.com>

Regarding your HTML WG timeline for Last Call,  you stated that if 
anyone has questions we can ask them here[1].

Question: you have put a deadline on when bugs can be filed and still 
treated as bugs. After the date, any new bugs are treated as Last Call 
comments. However, you have nothing in the timeline about restrictions 
on the editor's actions, including his making unilateral and sweeping 
changes in the text. All you have is the following:

"Note: We're working with the editor to find ways to ensure tighter 
change control for the draft after the cutoff date, but we do not have 
anything to announce on this front yet."

As an example of a recent addition that was added without any discussion 
in the HTML WG is his addition of a link to the WhatWG wiki in order for 
people to register canvas context types[2]. This was discovered purely 
by accident, and as far as I can tell, was an addition to the document 
not based on prior HTML WG discussion, or bug activity.

How can you say you have a timeline, with concrete dates and actions, 
when you don't have any guarantees of editor behavior during this time?

In addition, you say that bugs must be addressed by the editor by a 
certain date, but you don't say how they need to be addressed. The 
editor is fond of using NEEDSINFO, which I don't consider addressed, but 
does change the status to RESOLVED. Again, you're not addressing the 
reality of what exists in your timeline.

Lastly, I've had two surveyed issues waiting co-chair decision for four 
months now. Do you seriously believe you're going to be able to address 
issues in the timeline you're giving yourselves? Other than one word 

Your timeline does not reflect the reality of what is the HTML WG. 
Either that, or your timeline reflects the fact that the W3C is no 
longer going to attempt to meet the needs of all the web community, and 
you're just going to let the HTML5 editor do what he wants.


[1] http://lists.w3.org/Archives/Public/public-html/2010Sep/0074.html
[2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10556
Received on Wednesday, 8 September 2010 13:37:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:43:43 UTC