Reed Loden wrote:
On Wed, 07 Feb 2007 16:00:03 +0000
Gervase Markham <[EMAIL PROTECTED]> wrote:
- "websites-security" is created to deal with websites. Initial
membership is the same as webtools-security.
[Products: Websites]
Please do not include webtools-security in the membership of this
group. It should be a new group, as the websites are not related at all
to the webtools.
Well, it has to have an initial group population from somewhere. Where
do you suggest getting it? Is there a mailing list about this sort of
thing? Or an owner for "website security" who can provide me with a list?
- "update-security", renamed to "addons-security", becomes used for
addons issues (both the servers and the addons themselves). No
change in membership.
[Product: addons.mozilla.org]
What about inheritance for this group?
I wasn't planning on changing that either.
- Create a new "aus-security" group for AUS. People in the main
security group inherit membership of aus-security.
[Product: AUS]
Need to make sure morgamic is added to this group.
Let's work on adjusting group memberships as a second step, OK? :-)
"mozillacomconfidential" -> "mozilla-com-private"
"mozillaorgconfidential" -> "mozilla-org-private"
Please define the difference between mozilla-com-private and
mozilla-org-private as used in this context. Which components will
default to which of the two mozilla-*-private components?
I don't think any components will necessarily default to
mozilla-org-private. If there are components for Corporation internal IT
requests, I assume they will default to mozilla-com-private.
Gerv
_______________________________________________
dev-security mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security
