Improve licensing info #1599
Merged
Improve licensing info #1599
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
3 tasks
[why] It can be hard to find out which license a particular font is using. Therefore we add a new field to the fonts.json with an SPDX license identifier (if possible). [how] For fonts with a license that has no SPDX identifier we use a free `LicenseRef-*` identifier, but that reference is not solved in the fonts.json file. [note] Also correct some licensing info given in the license audit. Related: #1578 Suggested-by: Jan Christian Gruenhage <jan.christian@gruenhage.xyz> Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Finii
force-pushed
the
feature/licensing-info
branch
from
a678967 to
e28b51c
Compare
|
Fix typo, force push. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add SPDX license info
[why]
It can be hard to find out which license a particular font is using.
Therefore we add a new field to the fonts.json with an SPDX license
identifier (if possible).
[how]
For fonts with a license that has no SPDX identifier we use a free
LicenseRef-*identifier, but that reference is not solved in thefonts.json file.
[note]
Also correct some licensing info given in the license audit.
Related: #1578
Suggested-by: Jan Christian Gruenhage jan.christian@gruenhage.xyz
Requirements / Checklist
What does this Pull Request (PR) do?
How should this be manually tested?
Any background context you can provide?
What are the relevant tickets (if any)?
Screenshots (if appropriate or helpful)