New project mailing lists

[Richard Purdie]

On Tue, 2015-10-13 at 11:34 -0700, Khem Raj wrote:
> > On Oct 13, 2015, at 10:39 AM, Mark Hatle <mark.hatle at windriver.com> wrote:
> > 
> > On 10/13/15 12:36 PM, Khem Raj wrote:
> >> 
> >>> On Oct 13, 2015, at 10:33 AM, Philip Balister <philip at balister.org> wrote:
> >>> 
> >>> On 10/13/2015 01:28 PM, Paul Eggleton wrote:
> >>>> On Tuesday 13 October 2015 13:03:40 Philip Balister wrote:
> >>>>> At OEDEM we talked about creating a list:
> >>>>> 
> >>>>> openemebdded-architecture - Discussions about overall OpenEmbedded
> >>>>> Architecture and status
> >>>>> 
> >>>>> Any objections to the name and description? I'd like to ask Michael to
> >>>>> set this up.
> >> 
> >> what will this achieve that oe-devel can’t do ? people are already subscribed to oe-devel
> >> and prefixing with [architecture] prefix might be enough. We already use subject prefix filters on oe-devel
> >> messages.
> > 
> > The discussion was that most of us are filtering out oe-devel to the things we
> > care about.. and thus missing architectural discussions..
> > 
> 
> 
> It seems we want a new list for convenience which could otherwise be another filter on someones list ?
> oe-devel is far reaching then this new list would be, Its important to get opinion from developers
> and users who are at fringes of project too. If they don’t reciprocate, atleast they have the information
> thats being discussed. It will also have good learning for new folks who are looking out to learn about
> OE without much effort of advertising the new list.
> 
> > Architectural being more then just meta-openembedded, or oe-core... but layer
> > index, and other things affecting the overall infrastructure and architecture of
> > OpenEmbedded.
> 
> yes thats all part of open embedded
> 
> > 
> > At this point, I think a new list is the best answer..  while I don't really
> > want a new list -- the reality is without it a lot of us are going to miss
> > relevant discussions.
> 
> with a bit of discipline we can have it right. IMO its more important to let community have the convenience
> then few who can not set filters.

A quick poll of people in the room in Dublin suggested that near enough
everyone is having information filtering issues with the current lists.
There was also confusion about where archtiecture type discussion should
happen with some people thinking it was "core", some "oe-devel".

I appreciate that someone can filter by whether the mail contains
patches, equally I know I've missed the right magic prefix off on
occasion.

There is also a group of people who just don't want to see patches, they
do however want to see discussions about the architecture itself
changing. Expecting each one of these people to setup their own filters
is unrealistic.

So whilst "another list" is something which at first seems less than
ideal, there was a strong consensus of agreement in the room that when
you looked at the different options, it was the least worst alternative.

Cheers,

Richard