From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Guidelines for creating a layer
Date: Fri, 11 Nov 2011 09:17:51 -0500 [thread overview]
Message-ID: <4EBD2E8F.6060400@balister.org> (raw)
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?
Philip
-------- 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
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next reply other threads:[~2011-11-11 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 14:17 Philip Balister [this message]
2011-11-11 23:29 ` [oe] Guidelines for creating a layer Denys Dmytriyenko
2011-11-11 23:29 ` Denys Dmytriyenko
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=4EBD2E8F.6060400@balister.org \
--to=philip@balister.org \
--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.