overview-manual: licensing section fixes
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH v2 1/1 overview-manual: licensing section fixes
From: Michael Opdenacker <[email protected]>
Remove the reference to the GPL license, unnecessary in this part of the manual and pointing to a wrong link (LGPL instead of GPL).
Anyway, we have no authority to say that the MIT license is compatible with the GPL.
Also provide details about the MIT license through Wikipedia, instead of just the raw license text with no explanations through opensource.org.
Signed-off-by Michael Opdenacker <[email protected]>
--- documentation/overview-manual/development-environment.rst | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
documentation/overview-manual/development-environment.rst +2 -6
@@ -616,13 +616,9 @@ this history, you can find basic information here: 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 +license is distributed with that software. Patches to the Yocto Project follow the upstream licensing scheme. You can find information on the -MIT license -`here <https://www.opensource.org/licenses/mit-license.php>`__. You can -find information on the GNU GPL -`here <https://www.opensource.org/licenses/LGPL-3.0>`__. +MIT license `here <https://en.wikipedia.org/wiki/MIT_License>`__. 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
Signature · 1 line
2.25.1