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, 17 insertions, 0 deletions

diff --git a/COPYING.MIT b/COPYING.MIT
new file mode 100644
index 00000000..fb950dc6
--- /dev/null
+++ b/COPYING.MIT
@@ -0,0 +1,17 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy 
+of this software and associated documentation files (the "Software"), to deal 
+in the Software without restriction, including without limitation the rights 
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom the Software is 
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in 
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
+THE SOFTWARE.