Re: How to add features to HTML5 (Was: tracker already has ternary state - RAISED)

Hi laura, thanks for putting in the time to dig up past advice
pronouncements on the process issues we are currently discussing.

It is intersting to note that as Rob Burns recently claimed and Mike
Smith refuted, the wiki was one of the sources for issues to be added
to the issue tracker:

Dan Conolly wrote [1]:

"You three are welcome to start porting issues over from the
various sources we discussed:
http://www.w3.org/2007/10/18-html-wg-minutes#item02
i.e.
the wiki issues list http://esw.w3.org/topic/HTML
and my isues list/agenda http://www.w3.org/html/wg/il16
and Ian Hickson's IMAP folders
http://canvex.lazyilluminati.com/misc/cgi/issues.cgi/
and WG email
http://lists.w3.org/Archives/Public/public-html/"


This clearly suggests that the issue tracker is the correct repository
for proposals raised via the wiki and the HTML WG mailing list.


It is important that the Chairs  provide a clear and concise process ,
to clarify what is currently an unclear process, with participants,
editors and W3C staff at odds over what the process is.



[1] http://lists.w3.org/Archives/Public/www-archive/2007Oct/0057.html

2008/6/10 Laura Carlson <laura.lee.carlson@gmail.com>:
> Hi Chris and Dan,
>
> Ian wrote:
>
>> here's a look at how to propose new features [1].
>
> Is this an official HTML5 working group procedure?
>
>>> Where does bugzilla fit in?
>>> Where does issue tracker fit in?
>
>> Those are more useful for tracking problems and errors in the
>> spec, than for tracking new features.
>
> I did some research and found the message," Raising issues in a way
> that the editors will pay attention to them" [2] dated June 9, 2007
> which is one year ago today.
>
> The issue tracker was added last fall [3], [4], [5], [6].
>
> Bugzilla was added a few days ago to "To help keep track of proposals" [7].
>
> I appreciate that the process is evolving. But it is unclear how all
> of these pieces fit together and which ones this working group
> sanctions.
>
> Like I said in my other messages [8], [9], [10], [11] good policy,
> procedure, and flow-charting may be beneficial.
>
> Your guidance would be greatly appreciated.
>
> Thank you.
>
> Best Regards,
> Laura
>
> [1] http://lists.w3.org/Archives/Public/public-html/2008Jun/0140.html
> [2] http://lists.w3.org/Archives/Public/public-html/2007Jun/0003.html
> [3] http://lists.w3.org/Archives/Public/www-archive/2007Oct/0057.html
> [4] http://lists.w3.org/Archives/Public/public-html/2007Oct/0367.html
> [5] http://lists.w3.org/Archives/Public/public-html/2007Oct/0369.html
> [6] http://lists.w3.org/Archives/Public/public-html/2007Nov/0040.html
> [7] http://lists.w3.org/Archives/Public/public-html/2008Jun/0122.html
> [8] http://lists.w3.org/Archives/Public/www-archive/2008Jun/0036.html
> [9] http://lists.w3.org/Archives/Public/www-archive/2008Jun/0038.html
> [10] http://lists.w3.org/Archives/Public/www-archive/2008Jun/0040.html
> [11] http://lists.w3.org/Archives/Public/www-archive/2008Jun/0042.html
>
> --
> Laura L. Carlson
>



-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html

Received on Tuesday, 10 June 2008 07:36:19 UTC