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

>* Open Tracker Issues are issues with someone working on a change proposal [2].

I don't believe this is necessarily true.  

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.  And before yesterday when Sam issued several new Call for Change Proposals there were even more issues that the Responsible column had assigned to the Chairs.  In addition there are multiple issues where the Chairs have issued a Call for Change Proposals where no one has yet responded.

The Chairs have been trying to stage the number of outstanding Call for Change Proposals so as to not overwhelm the WG with requests which the WG would not be able to respond to.  I expect we may have to do this during Last Call as well depending on the volume of tracker issues and the number of active WG participants.

/paulc

[1] http://dev.w3.org/html5/status/issue-status.html 

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 7:43 AM
To: Maciej Stachowiak; HTML Accessibility Task Force; Janina Sajka
Cc: Matt May; Ian Hickson; Silvia Pfeiffer; Sam Ruby; HTML WG; Paul Cotton
Subject: Closing issues. Setting and meeting deadlines. (was Re: Issue-9 (video-accessibility): Chairs Solicit Proposals)

Maciej wrote:

> Speaking for myself and not necessarily my co-chairs (because I haven't
> asked their opinion): What I would prefer to see is that we resolve the
> issue based on some initial proposals, and then submit any proposals for
> further improvement via the bug process. If the bug process turns out to be
> insufficient for any further proposed improvements, then those specific
> improvements can be escalated to their own tracker issues.
> I do not think it is wise to continue recycling the same tracker issue for
> multiple rounds of changes. Handling things that way would lead to an issue
> that just stays open indefinitely.

From my reading of the HTML Working Group Decision Policy [1]:

* Open Tracker Issues are issues with someone working on a change proposal [2].

* If the change proposal is not done by the deadline, the issue will
be closed without prejudice and DEFERRED to the NEXT VERSION of HTML.

* An issue that is closed without prejudice in this way can only be
re-raised with approval of the HTML Chairs. It is an ENDPOINT for the
escalation process.

Is this correct?

Thanks.

Best Regards,
Laura

[1] http://dev.w3.org/html5/decision-policy/decision-policy.html

[2] The default deadline to complete a Change Proposal is ONE MONTH
from the time someone volunteers. The chairs may grant a longer
deadline for complex issues on request.

-- 
Laura L. Carlson

Received on Thursday, 4 March 2010 14:16:21 UTC