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

[Bug 8896] Clarify that anyone who is dissatisfied with a bug resolution may reopen or escalate

From: <bugzilla@wiggum.w3.org>
Date: Wed, 10 Mar 2010 23:27:16 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NpVJ6-0007MT-5x@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8896





--- Comment #2 from Maciej Stachowiak <mjs@apple.com>  2010-03-10 23:27:15 ---
(In reply to comment #1)
> It would be useful for the "decision policy" document to note how to watch the
> bugzilla changes which note bug resolutions and submitters agreement (or lack
> of response or whatever that might lead to a comment being "closed" without
> additional working group review.)
> 
> It's difficult to figure this out. I think one might, for example, monitor
> public-html-bugzilla@w3.org but that stream includes all kinds of bugzilla
> updates. is there a better way of monitoring when bugs are moved from NEW or
> ASSIGNED?
> 
> The current charter http://www.w3.org/2007/03/HTML-WG-charter section 6 says
> that communication happens on public-html@w3.org.
> 
> The working group home page http://www.w3.org/html/wg/ does point to a list of
> working group mailing lists, and public-html-bugzilla@w3.org is listed as one
> of the 10 mailing lists that might concern HTML, but it took some poking around
> to figure this out. 
> 

There's a couple of ways to track what happens in bugzilla:

1) You can subscribe to or read the archives of public-html-bugzilla, though as
you note that gives you a flood of irrelevant info.

2) You can add yourself to the Cc list of specific bugs you are interested in.

3) You can regularly do a bugzilla search query for bugs that have moved to
state RESOLVED in some period of time (e.g. weekly). That's what I do to gather
monthly bug stats, and Laura Carlson does it weekly for a subset of the bugs.

I agree it would be good to document these, though it seems like a separate
issue from the original substance of this bug.

We could also add additional ways, for example it may be possible to set up a
mailing list that gets mail only when a bug moves into RESOLVED state. I can
ask our Team Contacts about the feasibility of doing that.


-- 
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, 10 March 2010 23:27:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 March 2010 23:27:19 GMT