diff options
Diffstat (limited to 'documentation/dev-manual/dev-manual-newbie.xml')
-rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 78 |
1 files changed, 1 insertions, 77 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index a881295ce0..aca292063e 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
@@ -317,7 +317,7 @@ | |||
317 | Separate the project's Metadata and code by using | 317 | Separate the project's Metadata and code by using |
318 | separate Git repositories. | 318 | separate Git repositories. |
319 | See the | 319 | See the |
320 | "<ulink url='&YOCTO_DOC_REF_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>" | 320 | "<ulink url='&YOCTO_DOCS_REF_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>" |
321 | section for information on these repositories. | 321 | section for information on these repositories. |
322 | See the | 322 | See the |
323 | "<link linkend='getting-setup'>Getting Set Up</link>" | 323 | "<link linkend='getting-setup'>Getting Set Up</link>" |
@@ -354,82 +354,6 @@ | |||
354 | </section> | 354 | </section> |
355 | </section> | 355 | </section> |
356 | 356 | ||
357 | <section id='licensing'> | ||
358 | <title>Licensing</title> | ||
359 | |||
360 | <para> | ||
361 | Because open source projects are open to the public, they have different licensing structures in place. | ||
362 | License evolution for both Open Source and Free Software has an interesting history. | ||
363 | If you are interested in this history, you can find basic information here: | ||
364 | <itemizedlist> | ||
365 | <listitem><para><ulink url='http://en.wikipedia.org/wiki/Open-source_license'>Open source license history</ulink> | ||
366 | </para></listitem> | ||
367 | <listitem><para><ulink url='http://en.wikipedia.org/wiki/Free_software_license'>Free software license | ||
368 | history</ulink></para></listitem> | ||
369 | </itemizedlist> | ||
370 | </para> | ||
371 | |||
372 | <para> | ||
373 | In general, the Yocto Project is broadly licensed under the Massachusetts Institute of Technology | ||
374 | (MIT) License. | ||
375 | MIT licensing permits the reuse of software within proprietary software as long as the | ||
376 | license is distributed with that software. | ||
377 | MIT is also compatible with the GNU General Public License (GPL). | ||
378 | Patches to the Yocto Project follow the upstream licensing scheme. | ||
379 | You can find information on the MIT license | ||
380 | <ulink url='http://www.opensource.org/licenses/mit-license.php'>here</ulink>. | ||
381 | You can find information on the GNU GPL <ulink url='http://www.opensource.org/licenses/LGPL-3.0'> | ||
382 | here</ulink>. | ||
383 | </para> | ||
384 | |||
385 | <para> | ||
386 | When you build an image using the Yocto Project, the build process uses a | ||
387 | known list of licenses to ensure compliance. | ||
388 | You can find this list in the | ||
389 | <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink> at | ||
390 | <filename>meta/files/common-licenses</filename>. | ||
391 | Once the build completes, the list of all licenses found and used during that build are | ||
392 | kept in the | ||
393 | <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink> | ||
394 | at <filename>tmp/deploy/licenses</filename>. | ||
395 | </para> | ||
396 | |||
397 | <para> | ||
398 | If a module requires a license that is not in the base list, the build process | ||
399 | generates a warning during the build. | ||
400 | These tools make it easier for a developer to be certain of the licenses with which | ||
401 | their shipped products must comply. | ||
402 | However, even with these tools it is still up to the developer to resolve potential licensing issues. | ||
403 | </para> | ||
404 | |||
405 | <para> | ||
406 | The base list of licenses used by the build process is a combination of the Software Package | ||
407 | Data Exchange (SPDX) list and the Open Source Initiative (OSI) projects. | ||
408 | <ulink url='http://spdx.org'>SPDX Group</ulink> is a working group of the Linux Foundation | ||
409 | that maintains a specification | ||
410 | for a standard format for communicating the components, licenses, and copyrights | ||
411 | associated with a software package. | ||
412 | <ulink url='http://opensource.org'>OSI</ulink> is a corporation dedicated to the Open Source | ||
413 | Definition and the effort for reviewing and approving licenses that | ||
414 | conform to the Open Source Definition (OSD). | ||
415 | </para> | ||
416 | |||
417 | <para> | ||
418 | You can find a list of the combined SPDX and OSI licenses that the | ||
419 | Yocto Project uses in the | ||
420 | <filename>meta/files/common-licenses</filename> directory in your | ||
421 | <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>. | ||
422 | </para> | ||
423 | |||
424 | <para> | ||
425 | For information that can help you maintain compliance with various | ||
426 | open source licensing during the lifecycle of a product created using | ||
427 | the Yocto Project, see the | ||
428 | "<link linkend='maintaining-open-source-license-compliance-during-your-products-lifecycle'>Maintaining Open Source License Compliance During Your Product's Lifecycle</link>" | ||
429 | section. | ||
430 | </para> | ||
431 | </section> | ||
432 | |||
433 | <section id='git'> | 357 | <section id='git'> |
434 | <title>Git</title> | 358 | <title>Git</title> |
435 | 359 | ||