Licensing

From Apertis
Jump to: navigation, search

A project can include a number of licenses for different parts:

Organise your license files

It is very common to see only one COPYING file in a project which contains only a license text, and it is also common to see the images and documentation be shipped either under a license which is best suited for code (that is to say, impossible for images and documentation to comply with) or without proper licensing.

Licensing all parts of your project appropriately is not complicated and we highly recommend that you do so. Your typical directory structure should look something like:

<project>
↳COPYING
↳COPYING.MPL

The COPYING file should contain information about all parts of the project. For example, it could look like:

<project> is an Apertis project and follows the licensing guidelines as 
specified at https://wiki.apertis.org/Licensing.

Code
----
All code in this project is licensed under the Mozilla Public License Version 
2.0. See COPYING.MPL for the full license text.

Images
------
All icons and other images in this project are licensed under CC BY-SA 4.0
International. For information about this license, see
https://creativecommons.org/licenses/by-sa/4.0/

Documentation
-------------
All documentation in this project is licensed under CC BY-SA 4.0 International.
For information about the license, see
https://creativecommons.org/licenses/by-sa/4.0/

Your COPYING.MPL should contain the full license text for the Mozilla Public License Version 2.0. You may also need to have other license-specific COPYING files, depending on your project.

In this case, we include a COPYING.MPL to comply with the MPL 2.0 as it requires the full license text to be included in your project, but we do not have a COPYING.CC-BY-SA because the CC BY-SA 4.0 license does not require the license text to be distributed (but you may include it if you wish to do so).

Personal tools
Namespaces

Variants
Actions
Navigation
Tools