According to the Last Call timeline, starting tomorrow (Oct 1) all new
bugs in the HTML WG bugzilla data are automatically labeled Last Call
comments, which is somewhat equivalent to being made an issue, directly.
We can also make Last Call comments here to this email list.
I have questions on how this will work:
Do we need to provide marking to ensure that a comment to this email
list is treated formally as a Last Call comment?
Will each Last Call comment be assigned an Issue identifier, so that it
may be tracked? How can we ensure this happens?
Should we use a particular template in order to ensure consistency with
Last Call comments? Would the existing Change Proposal template [2] be a
good guideline?
Should we address LC comments to all HTML WG documents to this email
list, or only those related to the HTML5 spec?
Existing bugs will still go through the Decision process, albeit in an
abbreviated manner. For instance, if I read the timeline correctly,
there will not be time for surveys. Regardless, the Decision Process
addresses these bugs through Change Proposals. To bring this up again,
because the question was not definitively answered by the co-chairs or
the W3C management: can non-HTML WG members write change proposals? If
not, how do we ensure our concerns about issues get addressed?
Thank you for clarifications.
Shelley Powers
[1] http://www.w3.org/QA/2010/09/html5_getting_to_last_call.html
[2] http://www.w3.org/html/wg/wiki/ChangeProposalTemplate
