Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>
Cc: yocto <yocto@yoctoproject.org>, poky <poky@yoctoproject.org>
Subject: Re: Adding extra metadata to Yocto/Poky
Date: Wed, 08 Dec 2010 14:23:47 +0000	[thread overview]
Message-ID: <1291818227.1554.589.camel@rex> (raw)
In-Reply-To: <AANLkTimCmmksmkyD+a6CaWuazDTRCM+xZ-c8aZmRBF_Q@mail.gmail.com>

On Wed, 2010-12-08 at 07:08 -0700, Chris Larson wrote:
> On Wed, Dec 8, 2010 at 5:49 AM, Richard Purdie <rpurdie@linux.intel.com> wrote:
> > 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? :)
> 
> This seems fine to me as an area to hash out good practices and
> experiment, as long as we don't expect to use this structure long
> term.  It makes sense for the core layers to be in one repo, but it
> makes more sense to use one git repository per external layer, imo.
> Is that the intent, or am I misunderstanding its purpose?

That is the intent but we don't currently have the tooling to make repos
per external layer work nicely for the end user (not that I think its
too hard to create). This repo give us a way to experiment with
splitting things up whilst still not hurting the end user experience too
much.

So its not the final solution, just what I think might be a good way to
start hashing things out.

Cheers,

Richard




  reply	other threads:[~2010-12-08 14:24 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 [this message]
2010-12-08 17:43 ` Darren Hart

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=1291818227.1554.589.camel@rex \
    --to=rpurdie@linux.intel.com \
    --cc=clarson@kergoth.com \
    --cc=poky@yoctoproject.org \
    --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