Simplify licensing documentation

We have multiple locations where the licensing of Apertis is explained.
Simplfy/merge these explanations.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

content/developer/licensing.md

-+++
-short-description = "A summary of licensing implications"
-license = "CC-BY-SAv4.0"
-title = "Application Development: Choose a license for your application"
-weight = 100
-aliases = [ "/old-developer/latest/licensing.html", "/old-developer/v2019/licensing.html", "/old-developer/v2020/licensing.html", "/old-developer/v2021pre/licensing.html", "/old-developer/v2022dev0/licensing.html",]
-outputs = [ "html", "pdf-in",]
-date = "2016-12-07"
-+++
-
-You can chose any license that you wish for your application. If you use any of the Apertis libraries, you will still be able to keep your application closed source or open source.
-
-Apertis is a Free software platform. If you wish to follow the licensing model of Apertis, you can find further information in the [platform licensing](https://wiki.apertis.org/Licensing) guide.
-
-It is good practice to include information about copyright and the license at the top of each code file. This is often referred to as the header.
-
-For example, a copyright notice can look like this:
-```
-   /*
-    * Copyright © 2015, 2016 Anita Developer <a.developer@example.com>
-    */
-```
-
-If you use a Free software license, you will need to follow the guidelines provided by that license. We recommend that you also include the [SPDX license identifier](https://spdx.org/licenses/). For example, the license header for MPL 2.0 would look like this:
-```
-    /*
-     * Copyright © 2015, 2016 Anita Developer <a.developer@example.com>
-     *
-     * SPDX-License-Identifier: MPL-2.0
-     * This Source Code Form is subject to the terms of the Mozilla Public
-     * License, v. 2.0. If a copy of the MPL was not distributed with this
-     * file, You can obtain one at http://mozilla.org/MPL/2.0/.
-     */
-```
-
-The license you choose will not affect your ability to [distribute the application]( {{< ref "canterbury-legacy-application-framework.md" >}} ) through the Apertis app store.

content/policies/about_apertis.md

@@ -26,20 +26,3 @@ information (for example, web navigation, weather information,
 geolocation, contacts, *etc*.) and entertainment (for example, radio,
 music, videos, *etc*.) features, in an app-centric fashion. It is
 updated regularly to keep track of features and security fixes.
-
-## Licenses
-
-Apertis is primarily licensed under the [Mozilla Public License
-Version 2.0](https://www.mozilla.org/en-US/MPL/2.0/), with images and
-documentation licensed under [CC
-BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/legalcode).
-Individual You can find more information about the licensing for each repository in
-the `COPYING` files in each repository.
-
-Apertis also makes use of other projects such as the Linux kernel,
-WebKit and GNOME libraries which may be licensed under different terms.
-You can find further information about licenses for these projects from
-the projects themselves.
-
-You must ensure that you comply with all licensing terms when you use or
-modify Apertis.

content/policies/license-applying.md

@@ -5,29 +5,49 @@ aliases = [
 	"/old-designs/latest/license-applying.html",
 	"/old-designs/v2020/license-applying.html",
 	"/old-designs/v2021dev3/license-applying.html",
+	"/old-developer/latest/licensing.html",
+	"/old-developer/v2019/licensing.html",
+	"/old-developer/v2020/licensing.html",
+	"/old-developer/v2021pre/licensing.html",
+	"/old-developer/v2022dev0/licensing.html",
 ]
 outputs = [ "html", "pdf-in",]
 date = "2019-10-22"
 +++
 
-Apertis code, including build scripts, helpers and recipes, is licensed under the
+Apertis code, including build scripts, helpers and recipes, is primarily
+licensed under the
 [Mozilla Public License Version 2.0](https://www.mozilla.org/en-US/MPL/2.0/).
 Images (such as icons) and documentation in Apertis are licensed under the
 [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/)
 (CC BY-SA 4.0) license.
 
+Apertis also makes use of other projects which may have other licenses, such as
+the [GPL and LGPL](https://www.gnu.org/licenses/licenses.html). For example,
+this includes projects such as the Linux kernel, WebKit and GLib.
+
+You can find more information about the licensing for each component in
+the `COPYING` files in each components repository.
+
 When you contribute to any Apertis code repository, you are agreeing to license
 your work under the same license as the rest of the code in the repository.
 
-If you are
-[creating a new Apertis project]( {{< ref "module_setup.md" >}} ),
-the code must be licensed under the MPL 2.0, unless there’s a good reason for it
-to be licensed differently.
+If you are contributing software components to Apertis, these should be
+licensed under a
+[suitable open source license]({{< ref "license-expectations.md" >}}). The
+preferred license for Apertis is the MPL 2.0, unless there’s a good reason for
+it to be licensed differently.
 
-Apertis also makes use of other projects which may have other licenses, such as
-the [GPL and LGPL](https://www.gnu.org/licenses/licenses.html). For example,
-this includes projects such as the Linux kernel, WebKit and GLib.
+When building an application on top of Apertis (and do not intend to contribute
+it back to the Apertis project) you can choose any license that you wish for
+your application. However, care should be taken to ensure that your license is
+compatible with any libraries that you may use provided by the Apertis
+platform.
 
+{{% notice warning %}}
+You must ensure that you comply with all licensing terms when you use or
+modify Apertis.
+{{% /notice %}}
 
 ## Licensing of code
 
@@ -107,12 +127,12 @@ license text to be distributed (but you may include it if you wish to do so).
 
 ### Add license headers to each file
 
-A `license header` is a comment which is added to the top of a code file. It
-consists of a `copyright notice`, the SPDX license identifier and a license
-blurb which is provided with the license. The license header for a specific
-file must contain only copyright holders of content which is in that file. This
-means that the license header in each of your project files are likely to list
-different copyright holders.
+It is good practice to include a `license header` to the top of a code file. It
+is a comment that typically consists of a `copyright notice`, the SPDX license
+identifier and a license blurb which is provided with the license. The license
+header for a specific file must contain only copyright holders of content which
+is in that file. This means that the license header in each of your project
+files are likely to list different copyright holders.
 
 The copyright notice will normally contain `Copyright ©` followed by the
 copyright years and the copyright holder. It is recommended that you also