license: clarify the licensing for the project's metadata

Presently, the recipe files in meta-freescale are under an ambiguous
license. There is a EULA file at the root, but it's clearly not meant
to apply as the default license as it is only explicitly called out in
a few recipes and mirrors the language of the LSDK. The yocto upstream
projects are meant to be distributed under a more liberal license than
the LSDK.

There are several licenses listed is custom-licenses/, but those again
only apply to specific recipes (e.g. NXP-Binary-EULA).

The license for the recipes themselves (and for the layer metadata, etc.)
is not clear and is problematic when attempting to host a mirror of this
code. So, add a LICENSE file that describes this situation, and provide
a reference copy of the MIT license (taken from poky/meta/).

Signed-off-by: Dima Zavin <dmitriyz@waymo.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

1 files changed, 12 insertions, 0 deletions

diff --git a/LICENSE b/LICENSE
new file mode 100644
index 00000000..17964fe5
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,12 @@
+Different components of meta-freescale are under different licenses (a mix
+of MIT and proprietary). Please see:
+
+COPYING.MIT (MIT)
+custom-licenses/* (Various EULAs, included by recipes)
+
+All metadata is MIT licensed unless otherwise stated. Source code and binaries
+included in tree for individual recipes are 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.