Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

spec: Add a paragraph about which license to put in <project_license> #313

Merged
merged 1 commit into from Apr 13, 2021
Merged

spec: Add a paragraph about which license to put in <project_license> #313

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 docs/xml/metainfo-component.xml
View file
Open in desktop
@@ -1047,6 +1047,13 @@
<code>LicenseRef-proprietary</code> can be used to denote a proprietary license, with an optional URL to the license text following after
a <code>=</code> sign.
</para>
<para>
The license given in the <literal>project_license</literal> 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
<literal>project_license</literal>, as that could confuse users. In particular, the <literal>CC-BY-SA-3.0</literal> license which is commonly
used for documentation is not an (FSF or OSI) approved license for free software, so including it in <literal>project_license</literal> results in the
project as a whole being considered non-free.
</para>
<para>
Although the <literal>project_license</literal> tag is not mandatory, it is highly recommended to include it.
</para>