All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC Creation of a meta-telephony repository
Date: Fri, 11 Nov 2011 11:45:52 +0100	[thread overview]
Message-ID: <j9iud0$16r$1@dough.gmane.org> (raw)
In-Reply-To: <4EBCEE8B.10802@freyther.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 11-11-11 10:44, Holger Freyther schreef:
> On 11/10/2011 10:01 PM, Denys Dmytriyenko wrote:
> 
>>> I haven't seen enough reason to place the burden for this layer on
>>> the OE admin team instead of doing 'self' hosting on
>>> gitorious/github/etc/
>> 
>> Well, first of all, when we had constrained resources at oe.org, we
>> were trying to limit the number of commercial layers, assuming that the
>> company behind such layer is well capable of providing hosting for
>> their product. That would mean BSP layers from semis, like Intel, TI,
>> Freescale etc. or commercial distro layers from OSVs, such as Mentor,
>> Montavista etc. We always welcomed community layers on oe.org, even BSP
>> layers for platforms that had no official commercial support, but also
>> distro, apps and other layers, as long as they had "supported by
>> community" status.
> 
> Okay,
> 
> i don't mind hosting this myself (either gitorious or really myself).
> The reason to ask for hosting it on OE was making it easier to
> collaborate with OE members and making it more easy to find the
> repository.

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFOvPzgMkyGM64RGpERAjNiAJ4114dbMzlf07Jsa4IeGGmhxX1n2QCfchcF
PmSc2wSo80JoBXbPHZo5PgM=
=ulrG
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-11-11 10:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 14:58 RFC Creation of a meta-telephony repository Holger Freyther
2011-11-10 15:00 ` Philip Balister
2011-11-10 15:16 ` Paul Eggleton
2011-11-10 15:16 ` Martin Jansa
2011-11-10 16:35 ` Koen Kooi
2011-11-10 18:57   ` Denys Dmytriyenko
2011-11-10 20:25     ` Koen Kooi
2011-11-10 21:01       ` Denys Dmytriyenko
2011-11-11  9:44         ` Holger Freyther
2011-11-11 10:45           ` Koen Kooi [this message]
2011-11-11 12:54             ` Holger Freyther
2011-11-11 13:02               ` Phil Blundell
2011-11-11 13:08                 ` Paul Eggleton
2011-11-10 20:27   ` Florian Boor
2011-11-23 20:58 ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2011-11-10 15:49 Holger Freyther
2011-11-10 16:11 ` Philip Balister
2011-11-10 16:19   ` Paul Eggleton
2011-11-10 17:21 ` Phil Blundell
2011-11-10 20:22   ` Koen Kooi
2011-11-10 20:29     ` Florian Boor
2011-11-11  9:10       ` Koen Kooi
2011-11-10 21:07     ` Phil Blundell
2011-11-11  9:09       ` Koen Kooi
2011-11-11  9:25         ` Florian Boor
2011-11-11  9:38           ` Koen Kooi
2011-11-11  9:56             ` Florian Boor
2011-11-11 10:10           ` Phil Blundell
2011-11-11 10:37             ` Koen Kooi
2011-11-11 18:06 ` Denis 'GNUtoo' Carikli

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='j9iud0$16r$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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.