additional bugmail suggestion (was Re: [HTMLWG] CfC: Create a Mailing List for administrative matters and notifications?)

I didn't want to muddy the CfC thread, so taking this to a new thread.

I have an additional suggestion for the bug notifications:

I suggest that in addition to sending the new bug notifications to the
list, it would also make sense to send any bug status changes to the list
so people are aware when bugs are closed/invalidated etc. without having to
subscribe to a potentially lengthy discussion.

I think that if/when we create an administrative list, this extra admin
email might be appropriate.

Regards,
Silvia.


On Wed, Nov 7, 2012 at 7:40 AM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com>wrote:

> I like the idea of moving administrative matters to another list.
>
> Regards,
> Silvia.
>
>
> On Wed, Nov 7, 2012 at 6:53 AM, Sam Ruby <rubys@intertwingly.net> wrote:
>
>> On 10/22/2012 03:46 PM, Maciej Stachowiak wrote:
>>
>>>
>>> I've heard from some that the major objection to using public-html for
>>> certain technical discussions is not so much the other technical
>>> discussion, so much as administrative matters that are considered noise.
>>> Specifically, the things I have heard cited are bugzilla new bug
>>> notifications, and CFCs and other "call" type emails. How would folks
>>> feel about having a single unified technical discussion list, and then
>>> one or more separate (still mandatory-subscription) lists for
>>> administrative matters and notifications? If we can get consensus on
>>> such an approach, it might supersede the need for a survey, but I will
>>> try to get the survey out ASAP nonetheless, perhaps including this as an
>>> option.
>>>
>>
>> This proposal got some support and if there was any objections, I missed
>> it.  This Call for Consensus is intended to determine if there are indeed
>> any objections.
>>
>> So to be clear: the proposal is to create another mailing list and to
>> redirect the types of discussions described above to that mailing list.  If
>> this call passes, the name of that mailing list would be determined by W3C
>> staff, though constructive suggestions are welcome.
>>
>> If you have any comments or concerns about this CfC, please respond by
>> Wednesday, November 13th, 2012. Positive response is welcome and silence
>> will be considered as agreement with the proposal.
>>
>> If your comment is an objection, please clearly state that.
>>
>> - Sam Ruby
>>
>>
>>
>