Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [oe] Guidelines for creating a layer
Date: Fri, 11 Nov 2011 18:29:48 -0500	[thread overview]
Message-ID: <20111111232948.GE20602@denix.org> (raw)
In-Reply-To: <4EBD2E8F.6060400@balister.org>

On Fri, Nov 11, 2011 at 09:17:51AM -0500, Philip Balister wrote:
> Sorry to hack the subject and delete the earlier conversation, but Koen
> raises a good point here and I do not want it lost in the earlier
> discussion since I among others stopped reading the emails in detail.
> 
> Is there a good set of guidelines on the web site (not buried in a git
> repo) to guide people making the decision when to create a new layer, as
> opposed to contributing to an existing layer?
> 
> How do we make sure layers are well thought out and not people taking
> the path of least resistance?

I think this is a more generic and broad question to discuss it just between 
OE devs. So, my apologies for cross-post, but lets ask wider audience...

Denys


> -------- Original Message --------
> Subject: Re: [oe] RFC Creation of a meta-telephony repository
> Date: Fri, 11 Nov 2011 11:45:52 +0100
> From: Koen Kooi <koen@dominion.thruhere.net>
> Reply-To: openembedded-devel@lists.openembedded.org
> To: openembedded-devel@lists.openembedded.org
> 
> 
> Having worked with layers for quite a while now I go through the following
> list before creating one:
> 
> Does it need to be a layer? -> no -> send patches to existing layers
> 	|
> 	yes
> 	|
> Does it need to be a seperate repo? -> no -> send patches to existing repos
> 	|
> 	yes
> 	|
> Is github/gitorious/etc good enough? -> no -> ...
> 	|
> 	yes
> 	|
> Create repo + layer
> 
> And after a I while re-evaluate it.
> 
> regards,
> 
> Koen



           reply	other threads:[~2011-11-11 23:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4EBD2E8F.6060400@balister.org>]

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=20111111232948.GE20602@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.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