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

Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)

From: Shelley Powers <shelleypowers@burningbird.net>
Date: Thu, 04 Mar 2010 09:04:02 -0600
Message-ID: <4B8FCBE2.4010103@burningbird.net>
To: Paul Cotton <Paul.Cotton@microsoft.com>
CC: Laura Carlson <laura.lee.carlson@gmail.com>, Maciej Stachowiak <mjs@apple.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Janina Sajka <janina@rednote.net>, Matt May <mattmay@adobe.com>, Ian Hickson <ian@hixie.ch>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Sam Ruby <rubys@intertwingly.net>, HTML WG <public-html@w3.org>
The Tracker Issue page provides a better view of the issue, as well as 
more information. The Change Proposal page does not track the related 
emails. It doesn't even provide a good description of what the Issue is 
about. In addition, information from the Change Proposal is reflected 
back into the specification, as long as the issue is in certain states, 
and has the proper keywords to trigger this action. This latter action 
is particularly important, as people will be looking at the spec, not 
the Change Proposal Status page.

I would suggest just using the Change Proposal Status page as an 
at-a-glance report page, but ensure that the status is kept up to date 
with the Issue Tracker. In addition, when an issue is set to open, add 
the keywords to incorporate the issue into the spec. I've done so for 
all of my issues. If someone wants me to help them do the same for their 
issues, holler.

Shelley

Paul Cotton wrote:
> Now I understand your point better.  Personally I have been using the Change Proposal Status page to track all Tracker Issues and had not spent much time using the actual Tracker list of issues [1].
>
> Note it would appear that there are several issues in the Tracker list [1] that do not have the correct "State" recorded to reflect whether they are in the RAISED or OPEN states.  And there are no Trackers issues in the Pending Review state although the state name might appear to apply to when the WG is discussing one or more change proposals.
>
> I think the WG needs to decide how much effort we want to put into keeping the Tracker issue State correct when the information is already recorded in the Change Proposal Status page.
>
> Thanks for pointing out this situation.
>
> /paulc
>
> [1] http://www.w3.org/html/wg/tracker/issues
>
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> Tel: (425) 705-9596 Fax: (425) 936-7329
>
>
> -----Original Message-----
> From: Laura Carlson [mailto:laura.lee.carlson@gmail.com] 
> Sent: Thursday, March 04, 2010 9:27 AM
> To: Paul Cotton
> Cc: Maciej Stachowiak; HTML Accessibility Task Force; Janina Sajka; Matt May; Ian Hickson; Silvia Pfeiffer; Sam Ruby; HTML WG
> Subject: Re: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)
>
> Hi Paul,
>
> On Thu, Mar 4, 2010 at 8:15 AM, Paul Cotton <Paul.Cotton@microsoft.com> wrote:
>   
>>> * Open Tracker Issues are issues with someone working on a change proposal [2].
>>>       
>> I don't believe this is necessarily true.
>>     
>
> 2.b. in the document  says
>
> "Open Issue: Writing a Change Proposal
>     An issue with someone working on a change proposal is in the OPEN state."
>
> http://dev.w3.org/html5/decision-policy/decision-policy.html#escalation-step-2b
>
> Should that be reworded?
>
>   
>> For example if you examine the Change Proposal Status page [1] you will see that there at least one issue e.g. ISSUE-78 for which the Chairs have not yet issued a Call for Change Proposals.
>>     
>
> ISSUE-78  seems to be in the "raised" state not "open".
> http://www.w3.org/html/wg/tracker/issues/78
>
> Thanks.
>
> Best Regards,
> Laura
>
>   
Received on Thursday, 4 March 2010 15:04:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:03 GMT