From 18ef935cac53e7be2f0aa15830917fbed31af3a9 Mon Sep 17 00:00:00 2001 From: Philip Withnall Date: Tue, 13 Apr 2021 14:47:55 +0100 Subject: [PATCH] spec: Add a paragraph about which license to put in Signed-off-by: Philip Withnall Helps: #312 --- docs/xml/metainfo-component.xml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/xml/metainfo-component.xml b/docs/xml/metainfo-component.xml index 7227c4d4..e04c586e 100644 --- a/docs/xml/metainfo-component.xml +++ b/docs/xml/metainfo-component.xml @@ -1047,6 +1047,13 @@ LicenseRef-proprietary can be used to denote a proprietary license, with an optional URL to the license text following after a = sign. + + The license given in the project_license tag should be the ‘main’ license of the project. For a software project, this + is typically the license for the code. It is not recommended to include the license for accompanying documentation (for example) in + project_license, as that could confuse users. In particular, the CC-BY-SA-3.0 license which is commonly + used for documentation is not an (FSF or OSI) approved license for free software, so including it in project_license results in the + project as a whole being considered non-free. + Although the project_license tag is not mandatory, it is highly recommended to include it.