openstack team mailing list archive

[Thierry Carrez <thierry@xxxxxxxxxxxxx>]

Russell Bryant wrote:
> On 09/12/2012 08:56 PM, Syd (Sydney) Logan wrote:
>> Guess the only advantage would be to minimize the chance of someone
>> missing the security related messages in the noise of a heavy traffic
>> mailing list.
>>
>> Even if there were a specialized list, I’d think you’d want to cross
>> post security issues to all lists, depending on severity (and with
>> security, all issues are generally severe).
> 
> We have started posting the security advisories to the
> openstack-announce list, as well.  That should cover those wanting to
> watch out for them on a low volume mailing list.
> 
> I like the simple group of openstack@, openstack-dev@, and
> openstack-announce@.

That would be option B2 ("single user/general list, named openstack"):
openstack@xxxxxxxxxxxxxxxxxxx
openstack-announce@xxxxxxxxxxxxxxxxxxx
openstack-dev@xxxxxxxxxxxxxxxxxxx

I think it's the clearest to avoid cross-posting...

Reminder: here were the other options:

Option A1 ("separate operators, general named openstack-general"):
openstack-general@xxxxxxxxxxxxxxxxxxx
openstack-operators@xxxxxxxxxxxxxxxxxxx
openstack-announce@xxxxxxxxxxxxxxxxxxx
openstack-dev@xxxxxxxxxxxxxxxxxxx

Option A2 ("separate operators, general just named openstack)":
openstack@xxxxxxxxxxxxxxxxxxx
openstack-operators@xxxxxxxxxxxxxxxxxxx
openstack-announce@xxxxxxxxxxxxxxxxxxx
openstack-dev@xxxxxxxxxxxxxxxxxxx

Option B1 ("single user/general list, named openstack-user"):
openstack-user@xxxxxxxxxxxxxxxxxxx
openstack-announce@xxxxxxxxxxxxxxxxxxx
openstack-dev@xxxxxxxxxxxxxxxxxxx

Option Z ("keep current situation"):
openstack@xxxxxxxxxxxxxxxxxxx
openstack-operators@xxxxxxxxxxxxxxxxxxx
openstack-announce@xxxxxxxxxxxxxxxxxxx
openstack-dev@xxxxxxxxxxxxxxxxxxx

My own order of preference is A1, B2, A2, B1, Z. I'm fine with B2 if
people in -operators are OK with it.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack