1 files changed, 91 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/licensing.html b/documentation/getting-started/eclipse/html/getting-started/licensing.html
new file mode 100644
index 0000000000..ade868705c
--- /dev/null
+++ b/documentation/getting-started/eclipse/html/getting-started/licensing.html
@@ -0,0 +1,91 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.6. Licensing</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="Getting Started With Yocto Project">
+<link rel="up" href="overview-development-environment.html" title="Chapter 2. The Yocto Project Development Environment">
+<link rel="prev" href="yocto-project-repositories.html" title="2.5. Yocto Project Source Repositories">
+<link rel="next" href="recipe-syntax.html" title="2.7. Recipe Syntax">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.6. Licensing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="licensing"></a>2.6. Licensing</h2></div></div></div>
+<p>
+        Because open source projects are open to the public, they have
+        different licensing structures in place.
+        License evolution for both Open Source and Free Software has an
+        interesting history.
+        If you are interested in this history, you can find basic information
+        here:
+        </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>
+                <a class="ulink" href="http://en.wikipedia.org/wiki/Open-source_license" target="_self">Open source license history</a>
+                </p></li>
+<li class="listitem"><p>
+                <a class="ulink" href="http://en.wikipedia.org/wiki/Free_software_license" target="_self">Free software license history</a>
+                </p></li>
+</ul></div>
+<p>
+    </p>
+<p>
+        In general, the Yocto Project is broadly licensed under the
+        Massachusetts Institute of Technology (MIT) License.
+        MIT licensing permits the reuse of software within proprietary
+        software as long as the license is distributed with that software.
+        MIT is also compatible with the GNU General Public License (GPL).
+        Patches to the Yocto Project follow the upstream licensing scheme.
+        You can find information on the MIT license
+        <a class="ulink" href="http://www.opensource.org/licenses/mit-license.php" target="_self">here</a>.
+        You can find information on the GNU GPL
+        <a class="ulink" href="http://www.opensource.org/licenses/LGPL-3.0" target="_self">here</a>.
+    </p>
+<p>
+        When you build an image using the Yocto Project, the build process
+        uses a known list of licenses to ensure compliance.
+        You can find this list in the
+        <a class="link" href="../ref-manual/source-directory.html" target="_self">Source Directory</a>
+        at <code class="filename">meta/files/common-licenses</code>.
+        Once the build completes, the list of all licenses found and used
+        during that build are kept in the
+        <a class="link" href="../ref-manual/build-directory.html" target="_self">Build Directory</a>
+        at <code class="filename">tmp/deploy/licenses</code>.
+    </p>
+<p>
+        If a module requires a license that is not in the base list, the
+        build process generates a warning during the build.
+        These tools make it easier for a developer to be certain of the
+        licenses with which their shipped products must comply.
+        However, even with these tools it is still up to the developer to
+        resolve potential licensing issues.
+    </p>
+<p>
+        The base list of licenses used by the build process is a combination
+        of the Software Package Data Exchange (SPDX) list and the Open
+        Source Initiative (OSI) projects.
+        <a class="ulink" href="http://spdx.org" target="_self">SPDX Group</a> is a working group of
+        the Linux Foundation that maintains a specification for a standard
+        format for communicating the components, licenses, and copyrights
+        associated with a software package.
+        <a class="ulink" href="http://opensource.org" target="_self">OSI</a> is a corporation
+        dedicated to the Open Source Definition and the effort for reviewing
+        and approving licenses that conform to the Open Source Definition
+        (OSD).
+    </p>
+<p>
+        You can find a list of the combined SPDX and OSI licenses that the
+        Yocto Project uses in the
+        <code class="filename">meta/files/common-licenses</code> directory in your
+        <a class="link" href="../ref-manual/source-directory.html" target="_self">Source Directory</a>.
+    </p>
+<p>
+        For information that can help you maintain compliance with various
+        open source licensing during the lifecycle of a product created using
+        the Yocto Project, see the
+        "<a class="link" href="../dev-manual/maintaining-open-source-license-compliance-during-your-products-lifecycle.html" target="_self">Maintaining Open Source License Compliance During Your Product's Lifecycle</a>"
+        section in the Yocto Project Development Tasks Manual.
+    </p>
+</div></body>
+</html>

diff --git a/documentation/getting-started/eclipse/html/getting-started/licensing.html b/documentation/getting-started/eclipse/html/getting-started/licensing.html new file mode 100644 index 0000000000..ade868705c --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/licensing.html
@@ -0,0 +1,91 @@
	1	<html>
	2	<head>
	3	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
	4	<title>2.6. Licensing</title>
	5	<link rel="stylesheet" type="text/css" href="../book.css">
	6	<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
	7	<link rel="home" href="index.html" title="Getting Started With Yocto Project">
	8	<link rel="up" href="overview-development-environment.html" title="Chapter 2. The Yocto Project Development Environment">
	9	<link rel="prev" href="yocto-project-repositories.html" title="2.5. Yocto Project Source Repositories">
	10	<link rel="next" href="recipe-syntax.html" title="2.7. Recipe Syntax">
	11	</head>
	12	<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.6. Licensing">
	13	<div class="titlepage"><div><div><h2 class="title" style="clear: both">
	14	<a name="licensing"></a>2.6. Licensing</h2></div></div></div>
	15	<p>
	16	Because open source projects are open to the public, they have
	17	different licensing structures in place.
	18	License evolution for both Open Source and Free Software has an
	19	interesting history.
	20	If you are interested in this history, you can find basic information
	21	here:
	22	</p>
	23	<div class="itemizedlist"><ul class="itemizedlist" type="disc">
	24	<li class="listitem"><p>
	25	<a class="ulink" href="http://en.wikipedia.org/wiki/Open-source_license" target="_self">Open source license history</a>
	26	</p></li>
	27	<li class="listitem"><p>
	28	<a class="ulink" href="http://en.wikipedia.org/wiki/Free_software_license" target="_self">Free software license history</a>
	29	</p></li>
	30	</ul></div>
	31	<p>
	32	</p>
	33	<p>
	34	In general, the Yocto Project is broadly licensed under the
	35	Massachusetts Institute of Technology (MIT) License.
	36	MIT licensing permits the reuse of software within proprietary
	37	software as long as the license is distributed with that software.
	38	MIT is also compatible with the GNU General Public License (GPL).
	39	Patches to the Yocto Project follow the upstream licensing scheme.
	40	You can find information on the MIT license
	41	<a class="ulink" href="http://www.opensource.org/licenses/mit-license.php" target="_self">here</a>.
	42	You can find information on the GNU GPL
	43	<a class="ulink" href="http://www.opensource.org/licenses/LGPL-3.0" target="_self">here</a>.
	44	</p>
	45	<p>
	46	When you build an image using the Yocto Project, the build process
	47	uses a known list of licenses to ensure compliance.
	48	You can find this list in the
	49	<a class="link" href="../ref-manual/source-directory.html" target="_self">Source Directory</a>
	50	at <code class="filename">meta/files/common-licenses</code>.
	51	Once the build completes, the list of all licenses found and used
	52	during that build are kept in the
	53	<a class="link" href="../ref-manual/build-directory.html" target="_self">Build Directory</a>
	54	at <code class="filename">tmp/deploy/licenses</code>.
	55	</p>
	56	<p>
	57	If a module requires a license that is not in the base list, the
	58	build process generates a warning during the build.
	59	These tools make it easier for a developer to be certain of the
	60	licenses with which their shipped products must comply.
	61	However, even with these tools it is still up to the developer to
	62	resolve potential licensing issues.
	63	</p>
	64	<p>
	65	The base list of licenses used by the build process is a combination
	66	of the Software Package Data Exchange (SPDX) list and the Open
	67	Source Initiative (OSI) projects.
	68	<a class="ulink" href="http://spdx.org" target="_self">SPDX Group</a> is a working group of
	69	the Linux Foundation that maintains a specification for a standard
	70	format for communicating the components, licenses, and copyrights
	71	associated with a software package.
	72	<a class="ulink" href="http://opensource.org" target="_self">OSI</a> is a corporation
	73	dedicated to the Open Source Definition and the effort for reviewing
	74	and approving licenses that conform to the Open Source Definition
	75	(OSD).
	76	</p>
	77	<p>
	78	You can find a list of the combined SPDX and OSI licenses that the
	79	Yocto Project uses in the
	80	<code class="filename">meta/files/common-licenses</code> directory in your
	81	<a class="link" href="../ref-manual/source-directory.html" target="_self">Source Directory</a>.
	82	</p>
	83	<p>
	84	For information that can help you maintain compliance with various
	85	open source licensing during the lifecycle of a product created using
	86	the Yocto Project, see the
	87	"<a class="link" href="../dev-manual/maintaining-open-source-license-compliance-during-your-products-lifecycle.html" target="_self">Maintaining Open Source License Compliance During Your Product's Lifecycle</a>"
	88	section in the Yocto Project Development Tasks Manual.
	89	</p>
	90	</div></body>
	91	</html>