Open Stack

-----Original Message-----
From: Thierry Carrez <thierry at openstack.org>
Reply: OpenStack Development Mailing List (not for usage questions)
<openstack-dev at lists.openstack.org>
Date: February 27, 2017 at 11:19:25
To: openstack-dev at lists.openstack.org <openstack-dev at lists.openstack.org>
Subject:  Re: [openstack-dev] [all][swg] per-project "Business only"
moderated mailing lists

> Dean Troyer wrote:
> > On Mon, Feb 27, 2017 at 3:31 AM, Clint Byrum wrote:
> >> This is not for users who only want to see some projects. That is a well
> >> understood space and the mailman filtering does handle it. This is for
> >> those who want to monitor the overall health of the community, address
> >> issues with cross-project specs, or participate in so many projects it
> >> makes little sense to spend time filtering.
> >
> > Monday morning and the caffiene is just beginning to reach my brain,
> > but this seems counter-intuitive to me. I consider myself someone who
> > _does_ want to keep in touch with the majority of the community, and
> > breaking things into N additional mailing lists makes that harder, not
> > easier. I _do_ include core team updates, mascots, social meetings in
> > that set of things to pay a little attention to here, especially
> > around summit/PTG/Forum/etc times.
> >
> > I've seen a couple of descriptions of who this proposal is not
> > intended to address, who exactly is expected to benefit from more
> > mailing lists?
>
> I'm not (yet) convinced that getting rid of 10% of ML messages (the ones
> that would go to the -business lists) is worth the hassle of setting up
> 50 new lists, have people subscribe to them, and have overworked PTL
> moderate them...
>
> Also from my experience moderating such a -business list (the
> openstack-tc list) I can say that it takes significant effort to avoid
> having general-interest discussions there (or to close them when they
> start from an innocent thread). Over those 50+ -business mailing-lists
> I'm pretty sure a few would diverge and use the convenience of isolated
> discussions without "outsiders" potentially chiming in. And they would
> be pretty hard to detect...

I agree and would like to point out that it will likely confuse
newcomers. Where would they send their message to about whatever
feature their management is pressuring them to develop? Most likely
they'll try openstack-{project} first and then the PTL + their team
will have to read through it and guide the person to the openstack-dev
list. Core project teams already occasionally bicker over changes
being approved that one half wouldn't have approved. This will
introduce yet another place for subjective reasoning between trusted
members of the community.

I'm not sure there's a great deal of value in those lists considering
the likely costs.

--
Ian Cordasco