Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Andre McCurdy <armccurdy@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: Fri, 31 Jul 2015 14:41:58 +0300	[thread overview]
Message-ID: <55BB5F06.4010901@linux.intel.com> (raw)
In-Reply-To: <CAJ86T=UHTjTA7S_4EV66VEUoaRhYmaYveVcfxbqzVJsxZ4s6dg@mail.gmail.com>

On 07/31/2015 02:14 AM, Andre McCurdy wrote:

> The number of high quality recipes which can be maintained in oe-core
> depends on the number of developers actively using and contributing to
> oe-core. More active developers means more recipes can be maintained
> to a high quality.

My issue here is quality control. Someone still has to review the work 
of those volunteer developers, and take action when they fail to take 
action. Yocto at the moment does not have such a self-sustaining 
community process - it all still goes through 'core' oe-core developers, 
and those developers can't have any more workload.


Alex


  reply	other threads:[~2015-07-31 11:40 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 [this message]
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
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=55BB5F06.4010901@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox