[Openstack] Fwd: [Infra] administration of new mailinglists

Duncan McGreggor duncan at dreamhost.com
Wed May 30 16:26:51 UTC 2012


On Wed, May 30, 2012 at 10:11 AM, Thierry Carrez <thierry at openstack.org> wrote:
> Stefano Maffulli wrote:
>> On Tue 29 May 2012 10:36:05 AM PDT, James E. Blair wrote:
>>> Someone pointed out that since the security announcements _haven't_ been
>>> going to the announce list, but the main mailing list instead, that they
>>> are concerned that people may have missed them.  That seems like a very
>>> important and valid concern to me.
>>
>> Same here, I'm concerned that important information is sent out through
>> the wrong channel, not reaching the relevant people.
>
> I think the -announce list can be used as a reference channel, from
> where given posts can be highlighted in Twitter, blogposts, weekly
> newsletter, etc.
>
>>> To punt and say "people will see it on G+ or Twitter or whatever" (as
>>> stated elsewhere in this thread) isn't good enough for a project of this
>>> size.  What user should they follow?  What hashtag should they search
>>> for?  Fundamentally, the same problems will show up
>>
>> That's because, fundamentally, sending out a message to the relevant
>> people is a complex problem. Even if you setup the announce- list, you
>> still have to make sure that people will subscribe to it, and make sure
>> the announcers will use it properly. I assumed that since the list
>> existed formally but nobody cared to use it, it was not needed.
>
> In addition to mentioning the list on "getting started" pages, if you
> keep on pointing to the -announce archived posts when tweeting about
> something, some people will realize subscribing to the source will give
> them earlier access to the information. If they care enough, they will
> subscribe.
>
>>>> First of all, it's not clear to me *who* would need to send out
>>>> announcements. Can somebody start from there?
>>>
>>> Release team.  Security team.
>>
>> Sounds good enough for me. If those teams want to take care of it, I
>> don't have a problem, as long as they're happy with such a tool.
>> [...]
>> We clearly have two different use cases in mind. Since now it's clear
>> that the announce list is for the release and security team, I remove
>> my objection to have a list for announcements.
>
> I think we should also formally announce things like elections and
> election results on that (reference) channel. Obviously the news would
> be echoed in a lot of other channels, like the OpenStack blog/newsletter.

All good points. +1

d




More information about the Openstack mailing list