W3C home > Mailing lists > Public > public-html@w3.org > February 2010

Re: clarification on Adobe Blocking

From: Sam Ruby <rubys@intertwingly.net>
Date: Fri, 12 Feb 2010 15:23:32 -0500
Message-ID: <4B75B8C4.4080308@intertwingly.net>
To: Shelley Powers <shelley.just@gmail.com>
CC: Maciej Stachowiak <mjs@apple.com>, HTMLWG WG <public-html@w3.org>
Shelley Powers wrote:
> 
> 
> On Fri, Feb 12, 2010 at 2:10 PM, Maciej Stachowiak <mjs@apple.com 
> <mailto:mjs@apple.com>> wrote:
> 
> 
>     On Feb 12, 2010, at 12:06 PM, Shelley Powers wrote:
> 
>>
>>
>>     On Fri, Feb 12, 2010 at 2:00 PM, Maciej Stachowiak <mjs@apple.com
>>     <mailto:mjs@apple.com>> wrote:
>>
>>
>>         On Feb 12, 2010, at 11:39 AM, Shelley Powers wrote:
>>
>>>
>>>         Frankly, according to Sam's recent email in this thread about
>>>         the issue tracker and the procedure[3], once the issues I'm
>>>         writing Change Proposals for are properly upgraded to Open
>>>         issues, I'm blocking HTML5 more than Adobe, or any other
>>>         company: I have more issues in the issue tracker, all of
>>>         which, if I understand the process, are blocking until resolved.
>>
>>         As far as I'm concerned, raising issues in accordance with the
>>         process is not "blocking HTML5". It is an attempt to improve
>>         HTML5 (though of course others may disagree on what
>>         constitutes an improvement). I hope that is how you see it as
>>         well.
>>
>>         Regards,
>>         Maciej
>>
>>
>>     I agree. I see all of my bugs, issues, and change proposals as an
>>     attempt to improve or correct the HTM5 specification, and nothing
>>     more. 
>>
>>     I don't want to speak for others, but I would imagine this is the
>>     reason anyone brings up these concerns--and file bugs, raise
>>     issues, and write change proposals. The word "blocking" can be
>>     misinterpreted so easily.
>>
>>     But I'm not sure what I should do now when it comes to switching
>>     my issues from RAISED to OPEN, and to sync them with the HTML5
>>     spec? Should I try the issue edits myself? Or do I need to wait
>>     for someone else to do the work?  I'm wiling to do the work, and
>>     decipher the code necessary to make the connections, but if you
>>     all would rather I not, I'm just as happy for someone else to do
>>     the work -- as long as it gets done.
> 
>     It's best to add the status codes yourself if you can figure it out.
>     And it's fine to put your own issues in OPEN state (I will do it
>     myself when I get a chance if it's not done when I get around to
>     looking.)
> 
>     Regards,
>     Maciej
> 
> Cool. Will do tonight then.

I guess I didn't check email fast enough.  I've moved 81, 84, and 89-97 
to OPEN.

> Thanks!
> 
> Shelley

- Sam Ruby
Received on Friday, 12 February 2010 20:24:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:01 GMT