Christopher Blizzard wrote:
> Yes, please. In fact, I would just say shorten that to
> [EMAIL PROTECTED] instead of the overly-obscure
> [EMAIL PROTECTED] and just use [EMAIL PROTECTED]
"security" means different things to different people. I was thinking
that making the address of the list reflect its purpose rather
specifically will lower the amount of noise on the list.
"security" could be interpreted as security feature development, for
example, or as physical security ([EMAIL PROTECTED] is supposed to
be an engineering list, but it gets mail for campus security all the time).
[EMAIL PROTECTED] is long, but why do you call it
"obscure?" Seems pretty straightforward to me.
If people don't think that calling it security-bug-reports will cut down
on noise, or that brevity is more important, then we'll go with
[EMAIL PROTECTED]
What about the other list address, [EMAIL PROTECTED]?
> Seriously, a .announce style mailing list is a good idea.
Sounds fine to me, although I think the authoritative list should be a
webpage. We can do a mailing list too.
Ben Buchsch wrote:
> Everybody on the security bug group should be able to subscribe to the
> security bug reports list.
Everything I get from the bug reports address will be posted to a bug
right away, and the security group can view it there. That way we won't
have people filing duplicate bugs from the same problem report.
-Mitch
