From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel <openembedded-devel@openembedded.org>
Subject: OpenEmbedded Core - Ready for extended users
Date: Mon, 16 May 2011 12:26:58 +0100 [thread overview]
Message-ID: <1305545218.3424.29.camel@rex> (raw)
Hi,
The TSC has been tasked with working out how OE and Yocto could work
together and people have no doubt seen the discussions about OE-Core.
We're now pleased to formally announce that we feel OE-Core is ready for
exposure to more users and we'd like to encourage people to have a look
at it and experiment and develop with it.
Just to recap on the background for this, splitting up OE into
components has been a topic of discussion for a long time, certainly at
every OEDEM. Until now this hasn't happened partly due to resource
issues but also lack of tooling and the lack of a well thought out plan.
We now feel these issues have been addressed and that we have a good
plan in place. The promotion and use of layers is the only real way OE
can scale as a project yet stay maintainable and testable.
Things that aren't part of oe-core fall to the meta-oe layer which is
where we intend the current wider support contained in oe-devel to be
maintained. The people working on meta-oe so far would love to see more
contributions. Both repositories are currently working on a "pull" model
and people using them so far have felt a benefit to this for code
quality.
Discussion and development on oe-core is happening on the
openembedded-core mailing list since otherwise it would be hard to
filter out which patches and discussion were for which repository. We
look forward to seeing more people getting involved there!
(http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core)
Cheers,
Richard
(Communicating on behalf of the TSC)
next reply other threads:[~2011-05-16 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 11:26 Richard Purdie [this message]
2011-05-16 11:57 ` OpenEmbedded Core - Ready for extended users Koen Kooi
2011-05-16 12:52 ` Frans Meulenbroeks
2011-05-16 16:49 ` Phil Blundell
2011-05-17 6:23 ` Anders Darander
2011-05-17 6:38 ` Koen Kooi
2011-05-17 7:04 ` Anders Darander
2011-05-17 9:25 ` Petr Štetiar
2011-05-17 19:49 ` Richard Purdie
2011-05-19 6:12 ` Anders Darander
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=1305545218.3424.29.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.