Re: [hybi] Issue tracker

[Salvatore Loreto <[e-mail]>]

On 5/13/10 4:36 AM, Ian Hickson wrote:
> On Wed, 12 May 2010, Salvatore Loreto wrote:
>    
>> let me clarify about how we intend to work
>>
>> 1) Even if anyone is welcome to suggest issues,
>>     only the chairs are allowed to create a new issues!
>>
>> 2) We discuss the issues on the list for a while
>>
>> 3)  Issues related to WG documents will be initially
>>      assigned to one of the authors ( mainly because the tool allows to enter
>>      only one assignee ).
>>
>> 4) the assignee (or the WG document authors) come up with a form of words that
>>     they think matches the consensus and attach a diff to the trac
>>
>> 5) if there is a consensus on the text, the author will add it to the WG
>> document
>>     and the issues will be closed.
>>     if there is no consensus on the text go back to 4)
>>      
> That sounds like a huge amount of overhead. Here are the issues that I'm
> currently aware of for Web Sockets:
>
>     http://www.whatwg.org/issues/#websocket
>
>    
Hi Ian,
thanks for the pointer, and to have collect the WebSocket issues so far.
I wasn't not aware of the link, and I guess a lot of people were in the 
same situation.

as this is an IETF draft we have agreed to use the IETF Issue Tracker to 
collect them,
in this way give also a clear view of the amounts of issues that are 
related to each draft
and a clear knowledge of what those issues are.

> Do I need to send an e-mail for each one of these to raise it as an issue?
If you really think that an issue is important and it is worth to 
discuss it within the community,
then you should send by mail to the mailing list and ask to add it to 
the Issue tracker

>
> Doing so would likely take us ten times more time than just going ahead
> and fixing the problems would.
>    
in order to fix an issue and going ahead you have to discuss how to fix 
within the community
and allow all the people to contribute to the discussion.
Discussing and building consensus is always a time consuming task, but 
it helps a lot in writing
a good and robust protocol leveraging on the help and the experience of 
a lot of people

cheers
/Sal

-- 
Salvatore Loreto
www.sloreto.com