- Python 73.8%
- Jinja 18.5%
- Makefile 7.7%
|
|
||
|---|---|---|
| .forgejo | ||
| .reuse | ||
| .tito | ||
| data | ||
| grammar | ||
| LICENSES | ||
| tools | ||
| .gitignore | ||
| .packit.yaml | ||
| AUTHORS | ||
| CONTRIBUTING.md | ||
| DCO | ||
| fedora-license-data.spec | ||
| firmware.txt | ||
| how-to-release.md | ||
| Makefile | ||
| public-domain-text.txt | ||
| README.md | ||
| requirements.txt | ||
| TEMPLATE.toml | ||
| UltraPermissive.txt | ||
Fedora License Data Project
This project contains data for licenses that have been reviewed for use in the Fedora Linux project. For more on the criteria Fedora applies for such review, see License Approval
Licenses are categorized by their status of allowed (generally, or for specific uses) or not-allowed and published to Fedora Docs Legal. The data may include additional notes and provides mappings between the SPDX license expressions and the older Fedora "Callaway" short license names.
To request review of a new license for use in Fedora Linux, follow the process described at https://docs.fedoraproject.org/en-US/legal/license-review-process
The project also intends to publish the combined license information in a number of data file formats and provide a package in Fedora for other projects to reference, such as package building tools and package checking tools.
The Fedora Legal team is responsible for this project.
Contribution
To create a merge request to this project you must log in using Fedora OpenID. You can do that on SSO page.
Releases
Since the project is new and has many changes, we do releases very often. Currently it is every two weeks.
If you want faster releases you can use Copr project where automation builds an RPM after each pushed commit.
Releases are made directly from this repository according to the how-to-release.md document. Any downstream change in dist-git will be lost or cause us complications when making a release. Please send all contribs directly to the upstream repository.
Changes from this repository are propagated to fedora-legal-docs after a release.
Source and Output Formats
The source data are stored in TOML format. This was agreed as a simplest format for even non-technical contributors.
The RPM package contains the data in JSON format. If you need the data in a different format, you can send a merge request that converts the TOML data to a different format. We can have multiple output formats, but the source format has to be preserved.
Artifact
There is available an artifact fedora-licenses.json which is updated after every push to main branch. Note that some fields are deprecated, please check tools/fedora-license-schema.json.
The files for Fedora Docs Legal:
We produce License Policy file for Scancode Tookit
License
CC0-1.0
For detailed license information see REUSE DEP5 file.