Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	richard.purdie@linuxfoundation.org
Subject: [PATCH] LICENSE: Clarify what is meant by 'metadata'
Date: Mon, 27 Feb 2017 08:24:25 -0800	[thread overview]
Message-ID: <1488212665-27534-1-git-send-email-sgw@linux.intel.com> (raw)

The term metadata in the LICENSE text is unclear and recently
garnered some questions at ELC, so clarify metadata to include
bbclasses, which is and has been metadata as well as code.

Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
 LICENSE | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/LICENSE b/LICENSE
index 21fa6e6..9783ee5 100644
--- a/LICENSE
+++ b/LICENSE
@@ -6,9 +6,11 @@ meta/COPYING.MIT (MIT)
 meta-selftest/COPYING.MIT (MIT)
 meta-skeleton/COPYING.MIT (MIT)
 
-All metadata is MIT licensed unless otherwise stated. Source code
-included in tree for individual recipes is under the LICENSE stated in
-the associated recipe (.bb file) unless otherwise stated.
+All metadata files (including, but not limited to bb, bbappend,
+bbclass, inc and conf files) are MIT licensed unless otherwise stated.
+Source code included in tree for individual recipes is under the
+LICENSE stated in the associated recipe (.bb file) unless otherwise
+stated.
 
 License information for any other files is either explicitly stated 
 or defaults to GPL version 2.
-- 
2.7.4



             reply	other threads:[~2017-02-27 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 16:24 Saul Wold [this message]
2017-02-27 20:59 ` [PATCH] LICENSE: Clarify what is meant by 'metadata' Burton, Ross
2017-02-28 15:13   ` Saul Wold

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=1488212665-27534-1-git-send-email-sgw@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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