Guidelines for creating a layer

Guidelines for creating a layer

[Philip Balister]

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

Re: [oe] Guidelines for creating a layer

[Denys Dmytriyenko]

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

Re: Guidelines for creating a layer

[Denys Dmytriyenko]

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