From: Philip Balister <philip@balister.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
Khem Raj <raj.khem@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: meta-gplv2? [Was Re: parted_1.8.6.bb: add parted that not GPLv3]
Date: Mon, 10 Aug 2015 21:15:11 +0200 [thread overview]
Message-ID: <55C8F83F.4010003@balister.org> (raw)
In-Reply-To: <55C8956D.9080508@linux.intel.com>
On 08/10/2015 02:13 PM, Alexander Kanavin wrote:
> On 08/08/2015 08:09 PM, Philip Balister wrote:
>>> By 'self-sustaining' I mean 'being able to continuously produce quality
>>> work'. Looking at layers in meta-openembedded, not all of them are of
>>> high quality. Meta-gnome in particular is badly out of date, because no
>>> one wants to maintain it properly. If oe-core starts taking a lot more
>>> volunteer contributions, and the same thing happens (a volunteer
>>> contributes a large set of recipes, then disappears), what is supposed
>>> to happen then?
>>
>> You are missing the point. We now use layers to segregate sets of
>> recipes o stuff that is not interesting to many people and becomes
>> obsolete may decline without compromising heavily used layers. This is
>> all part of the evolution of OpenEmbedded over many, many years.
>>
>> If people lose interest in meta-gplv2, then so be it.
>
> This is perfectly fine with me. However, the subject has been whether
> the scope of *oe-core/poky* can be expanded without compromising
What is Poky?
Philip
> quality. I'm not sure at which point it got confused with general OE, so
> I can only refer you back to several emails up this thread:
>
> http://lists.openembedded.org/pipermail/openembedded-core/2015-July/108037.html
>
> http://lists.openembedded.org/pipermail/openembedded-core/2015-July/108167.html
>
> http://lists.openembedded.org/pipermail/openembedded-core/2015-July/108208.html
>
>
>
> Alex
>
next prev parent reply other threads:[~2015-08-10 19:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 7:14 [PATCH] parted_1.8.6.bb: add parted that not GPLv3 Lei Maohui
2015-07-09 11:33 ` alexander.kanavin
2015-07-09 11:38 ` Otavio Salvador
2015-07-10 22:31 ` Burton, Ross
2015-07-11 7:20 ` Andre McCurdy
2015-07-11 7:57 ` meta-gplv2? [Was Re: parted_1.8.6.bb: add parted that not GPLv3] Richard Purdie
2015-07-30 12:06 ` Alexander Kanavin
2015-07-30 23:14 ` Andre McCurdy
2015-07-31 11:41 ` Alexander Kanavin
2015-08-07 6:12 ` Khem Raj
2015-08-07 9:17 ` Philip Balister
2015-08-07 12:26 ` Alexander Kanavin
2015-08-07 19:16 ` Khem Raj
2015-08-08 17:09 ` Philip Balister
2015-08-10 12:13 ` Alexander Kanavin
2015-08-10 19:15 ` Philip Balister [this message]
2015-08-11 13:26 ` Alexander Kanavin
2015-08-11 15:46 ` Khem Raj
2015-08-11 20:36 ` Burton, Ross
2015-08-11 20:46 ` Otavio Salvador
2015-08-13 8:42 ` Philip Balister
2015-08-13 14:29 ` Mark Hatle
2015-08-14 1:43 ` Andre McCurdy
2015-08-18 9:03 ` Martin Jansa
2015-08-18 10:11 ` Richard Purdie
2015-08-18 11:16 ` Martin Jansa
2015-08-18 11:27 ` Richard Purdie
2015-08-11 23:26 ` Khem Raj
2015-08-12 14:49 ` Mark Hatle
2015-08-13 9:59 ` Anders Darander
2015-08-18 7:54 ` Martin Jansa
2015-08-18 11:12 ` Alexander Kanavin
2015-08-07 6:10 ` Khem Raj
2015-07-10 3:20 ` [PATCH] parted_1.8.6.bb: add parted that not GPLv3 Lei, Maohui
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=55C8F83F.4010003@balister.org \
--to=philip@balister.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.