[Bug 9315] Retain issue markers for issues that have timed out even during Last Call

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9315


Larry Masinter <lmm@acm.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lmm@acm.org




--- Comment #3 from Larry Masinter <lmm@acm.org>  2010-05-05 00:37:37 ---
Someone who has not been tracking the HTML working group process day to day
should be able to review which sections of the document for which there is
widely perceived problem but for which the issue was closed because there was
no concrete proposal delivered in time, especially since the timeouts have been
produced without any clear reasoning for when the deadline was set or any
consensus from the working group that the deadline was reasonable.

This "bug" in the process will be fixed when at least 2 out of 3 random
non-working group member would be able to tell that, say, the issue over the
"resource vs. representation" issue was only closed because Roy Fielding wasn't
willing to volunteer to work on the editing with a deadline to the chair's
satisfaction.

Whether you do it in the issue tracker or somewhere else isn't the question:
the question is whether this is actually an "open" process where issues are
closed, not because there is agreement, but because the issue timed out for
procedural rather than technical reasons.

"We have taken other means (e.g. WG home page) to make it easy for anyone to
set the set of closed issues, and soon, the separate set of postponed issues."

Whether this fixes the "bug" depends on whether the "other means" actually does
"make it easy" to see the set of postponed issues. Personally, I think the fact
that issues were postponed and not resolved should actually be marked in the
review copy rather than hidden somewhere in the working group home page
somewhere.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 5 May 2010 00:37:39 UTC