Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] [Bug 250763] Policy for AC bugzilla vs AC mailing list traffic  
Product/Component: Community / Architecture Council

Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
         AssignedTo|   |martin.oberhuber@windriver.c
                   |council@xxxxxxxxxxx         |om

--- Comment #1 from Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx>  2008-10-14 08:05:52 -0400 ---
Taking the mailinglist off CC, please comment on the bug if interested.

Personally, I think that while the bugzilla E-Mails can easily be perceived as
Spam, they are not. Just imagine the very same discussion happening directly on
the mailing list -- you'd get the same amount of traffic but not have the idea
that it is spam. Just organizing a discussion on bugzilla doesn't make that
discussion spam.

I do find the "dual notification" issue problematic though, and I don't find it
elegant that EAC bugzilla discussions are archived twice (on bugzilla and on
the mailing list).

Ideally, I think that the AC mailing list should be notified when a bug is
opened or newly CC'd to the EAC, and when a bug is resolved (such that all AC
members can see the resolution). For the times in-between, I'm fine with
on-demand E-Mail for those only who subscribe to the bug.

I think that bugzilla E-Mail Preferences should allow making this happen (just
disable E-Mail on new comments).

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Back to the top