All of lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <eha@doredevelopment.dk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] meta-openembedded layer for yocto hosted on oe.org
Date: Wed, 22 Dec 2010 06:43:09 +0100	[thread overview]
Message-ID: <1292996589.13721.1.camel@eha> (raw)
In-Reply-To: <AANLkTimv-=g7qhYQynPYi65Vp2sQk_a6mPUsVbh-M0eA@mail.gmail.com>

On Tue, 2010-12-21 at 18:51 +0100, Frans Meulenbroeks wrote:

> That leaves the question:
> Given the existence of Yocto in which parts do we see added value of
> OE and on which things should we as OE focus.
> But I guess this is more something for a different thread.

With or without Yocto, it seems like a good question to ask what we
would like to see improved in OE, ie. what would we like to see go into
OE within the next 1-2 years.

With that in mind, it should be somewhat easier to find out how to guide
OE community directions with relation to Yocto project.

I personally have the feeling that Yocto project have been given the
man-power to brute-force improve the quality of Poky/OpenEmbedded on a
day-by-day basis, and I expect they will be doing a good job at that.

One attractive direction of OE development would in my opinion to look a
bit further into the future, and work on fundamental improvements on
selected focus areas.

I imagine that Yocto will be expected to deliver continuous stream of
improvements to Poky, and will in practise be restricted to development
in microsteps of improvements.  Any improvements to OE that will require
a break in this continous stream is therefore something that OE might be
able to add value compared to what Yocto will deliver.

Of-course, I might just be beating a dead horse...

/Esben





  parent reply	other threads:[~2010-12-22  5:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 15:53 [RFC] meta-openembedded layer for yocto hosted on oe.org Koen Kooi
2010-12-20 16:56 ` Graeme Gregory
2010-12-20 17:16   ` Frans Meulenbroeks
2010-12-20 19:25     ` Maupin, Chase
2010-12-20 20:31       ` Frans Meulenbroeks
2010-12-21  8:16     ` Koen Kooi
2010-12-21 17:51       ` Frans Meulenbroeks
2010-12-21 18:41         ` Khem Raj
2010-12-21 20:28         ` Marcin Juszkiewicz
2010-12-21 21:16           ` Frans Meulenbroeks
2011-01-02 11:29           ` Frans Meulenbroeks
2010-12-22  5:43         ` Esben Haabendal [this message]
2010-12-21  9:45 ` Khem Raj
2010-12-21 18:48   ` Tom Rini
2010-12-21 19:25     ` Cliff Brake
2010-12-21 20:39       ` Chris Larson
2010-12-21 15:43 ` Cliff Brake
2010-12-21 16:25   ` Koen Kooi
2010-12-21 21:03     ` Denys Dmytriyenko
2010-12-22 11:19 ` Koen Kooi

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=1292996589.13721.1.camel@eha \
    --to=eha@doredevelopment.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.