Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe] Please merge lists openembedded-devel and openembedded-core again.
Date: Fri, 02 Sep 2011 18:00:16 +0100	[thread overview]
Message-ID: <1314982816.5939.616.camel@rex> (raw)
In-Reply-To: <1314976910.3526.36.camel@mattotaupa>

On Fri, 2011-09-02 at 17:21 +0200, Paul Menzel wrote:
> Am Freitag, den 02.09.2011, 14:19 +0100 schrieb Richard Purdie:
> > On Fri, 2011-09-02 at 10:05 -0300, Otavio Salvador wrote:
> > > On Fri, Sep 2, 2011 at 08:25, Paul Menzel wrote:
> 
> > > > it would be great if we could join the lists oe-devel and oe-core again.
> > > > As far as I know the only reason the list oe-core was created was to
> > > > discuss the initial setup and the creation of oe-core. Now that it has
> > > > been setup I do not see any reason to have two separate lists.
> > > >
> > > > I suggest to abandon/archive openembedded-core and use
> > > > openembedded-devel.
> > > 
> > > I fully support this merge.
> > 
> > I'm not so sure rushing into this is a great idea.
> 
> I interpret your answer that the merge is planned. What is the right
> time then?

Not planned, it has been talked about, particularly by the TSC members.

> > Speaking as someone who has problems trying to figure out where
> > patches are intended for
> 
> Also now you have to decide to what list to send them to. Now you just
> add a prefix/tag as is done on oe-devel already to differentiate between
> oe.dev and meta-oe.

Well, its relatively simple to decide if an email is appropriate for
oe-core or not.

Sure we could start asking people to use tags/prefixes but I fail to see
the advantage of putting more email in one place when a reasonable and
logical separate exists which actively helps people.

> > and who tracks whether they've been applied,
> 
> Well, the list is not a patch tracker. The patch queue is [1].

For various reasons its not how I track patches for OE-Core.

> > I do find the split useful...
> 
> Hmm, could you please elaborate?

We all try to find ways to make our workflows more efficient and to do
the best job we can at the things we attempt. The mailing list
separation actively helps me notice the most important things I need to
deal with. Now yes, I could use mail filters, I could do a variety of
things. Even with those I believe my response to various things would be
adversely impacted if we do merge the lists as with the best will in the
world, people sometimes don't do things like tags/prefixes/whatever and
its easier for anyone new to OE to get confused.

Cheers,

Richard




  parent reply	other threads:[~2011-09-02 17:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1314962732.3526.32.camel@mattotaupa>
2011-09-02 13:05 ` [oe] Please merge lists openembedded-devel and openembedded-core again Otavio Salvador
2011-09-02 13:19   ` Richard Purdie
2011-09-02 13:23     ` Otavio Salvador
2011-09-02 13:33       ` Koen Kooi
2011-09-02 13:53         ` Otavio Salvador
2011-09-02 16:47           ` Richard Purdie
2011-09-02 17:35             ` Otavio Salvador
2011-09-02 17:45               ` Richard Purdie
     [not found]     ` <1314976910.3526.36.camel@mattotaupa>
2011-09-02 17:00       ` Richard Purdie [this message]
2011-09-02 17:38         ` Otavio Salvador
2011-09-02 18:48       ` Phil Blundell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1314982816.5939.616.camel@rex \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox