From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <rpurdie@linux.intel.com>
Cc: yocto <yocto@yoctoproject.org>, poky <poky@yoctoproject.org>
Subject: Re: Adding extra metadata to Yocto/Poky
Date: Wed, 08 Dec 2010 09:43:31 -0800 [thread overview]
Message-ID: <4CFFC3C3.4090003@linux.intel.com> (raw)
In-Reply-To: <1291812548.1554.475.camel@rex>
On 12/08/2010 04:49 AM, Richard Purdie wrote:
> Hi,
>
> We're in a position where we have people wanting to extend Poky but
> wondering exactly how to add their own layer and make Poky useful for
> their specific use cases.
>
> This is a topic I want to work with the OE community on and have
> discussion about but equally, people are interested at the moment and we
> need something people can experiment with now so we can see what works
> and what doesn't.
>
> With this in mind I'm proposing we create a "poky-extras" repository
> which contains multiple user contributed layers.
>
> My proposed ground rules are:
>
> * it has the OE style open contributions model
> * consists of a set of layers, each clearly identified at the top level
> * each layer has a clearly named maintainer or maintainers
> * people respect the layer maintainers
> * layers are split into logical "topics" where at all possible
>
> Ultimately, the repo structure and some of the details could change but
> I'd like to experiment and see what we can come up with which is
> probably the only way we're going to move forward.
>
> Any comments, objections or better ideas? :)
Sounds like a good approach to me. What would the expectation of
"lifecycle" be? Will these layers move to the poky git repository after
some proven time to join things like meta-linaro and meta-demo (which
should be renamed meta-dlna) or should we move these layers to
poky-extras too?
--
Darren Hart
Yocto Linux Kernel
prev parent reply other threads:[~2010-12-08 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 12:49 Adding extra metadata to Yocto/Poky Richard Purdie
2010-12-08 14:08 ` Chris Larson
2010-12-08 14:23 ` Richard Purdie
2010-12-08 17:43 ` Darren Hart [this message]
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=4CFFC3C3.4090003@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=rpurdie@linux.intel.com \
--cc=yocto@yoctoproject.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