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

Re: Bug mail (Was: [Bug 10479] add role=radiogroup to details element)

From: Maciej Stachowiak <mjs@apple.com>
Date: Tue, 21 Sep 2010 08:48:50 -0700
Cc: public-html@w3.org
Message-id: <958FD61C-08FD-41D6-8032-4C0838FAD67A@apple.com>
To: Philip Jägenstedt <philipj@opera.com>

On Sep 21, 2010, at 5:36 AM, Philip Jägenstedt wrote:

> On Thu, 16 Sep 2010 23:30:37 +0200, Maciej Stachowiak <mjs@apple.com> wrote:
> 
>> Therefore, I suggest the following proposal:
>> 
>> - Stop sending notifications of keyword changes to public-html.
>> - Start sending new bug notifications to public-html, but only for components that represent a draft we have published at least once.
>> - Start sending new issue notifications from the tracker to public-html.
>> 
>> Note that this will result in the public-html mailing list receiving *more* bugmail than currently - about twice as much per month. However, the mail we get would be much more likely to be relevant and informative. We would get some mail on spam bugs, but also a lot of useful new bug notifications with full text of the bug.
>> 
>> What do Working Group members think of this proposal?
> 
> I'm not sure I'd see this as a great improvement. If the total volume increases and the amount of uninteresting mail remains fairly high, I'll keep skimming them very quickly or just marking them all as read. Most bugs that I've filed via the WHATWG review comment tool are editorial and I don't think the list needs to know about them.

You can preview whether the mail would be interesting by looking at mail with subject lines starting with "New" here: <http://lists.w3.org/Archives/Public/public-html-bugzilla/2010Sep/thread.html>. I read over all of the new bug messages, and it seemed like only a minority were editorial in nature. Many would affect browser behavior, often in ways that are relevant to compatibility.

> 
> Assuming that most bugs are uninteresting, couldn't we manually CC public-html on the few bugs that need wider discussion? If that's not technically possible, then having no automatic bugmail and having someone who cares enough manually write an email saying "what do you think about this bug?" would still be better than what we current have, for me at least.

We already have a process that requires manual flagging of bugs to bring them to the list's attention - either keyword them as "NE" or just send mail with a link to the bug. In practice, this seems to lead to the WG not getting enough information about incoming bugs.

No automatic notification at all would indeed result in less mail, but I'm not convinced it is best for the WG overall. I'd like to give the new setup a try, and see how it works in practice.

Regards,
Maciej
Received on Tuesday, 21 September 2010 15:49:32 GMT

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