|Max Mehl 4eaa1c4fd0 add installation via Guix||2 weeks ago|
|.reuse||3 months ago|
|LICENSES||6 months ago|
|docs||1 month ago|
|po||2 months ago|
|src/reuse||1 month ago|
|tests||1 month ago|
|.bumpversion.cfg||1 month ago|
|.editorconfig||1 month ago|
|.gitignore||2 months ago|
|.gitlab-ci.yml||2 months ago|
|.pre-commit-config.yaml||2 months ago|
|.pylintrc||2 months ago|
|AUTHORS.rst||1 month ago|
|CHANGELOG.md||1 month ago|
|Dockerfile||2 months ago|
|MANIFEST.in||2 months ago|
|Makefile||2 months ago|
|README.md||2 weeks ago|
|pyproject.toml||2 months ago|
|requirements.txt||2 months ago|
|setup.py||1 month ago|
|tox.ini||2 months ago|
reuse is a tool for compliance with the REUSE recommendations.
Copyright and licensing is difficult, especially when reusing software from different projects that are released under various different licenses. REUSE was started by the Free Software Foundation Europe (FSFE) to provide a set of recommendations to make licensing your Free Software projects easier. Not only do these recommendations make it easier for you to declare the licenses under which your works are released, but they also make it easier for a computer to understand how your project is licensed.
As a short summary, the recommendations are threefold:
You are recommended to read our tutorial for a step-by-step guide through these three steps. The FAQ covers basic questions about licensing, copyright, and more complex use cases. Advanced users and integrators will find the full specification helpful.
This tool exists to facilitate the developer in complying with the above recommendations.
There are other tools that have a lot more features and functionality surrounding the analysis and inspection of copyright and licenses in software projects. The REUSE helper tool, on the other hand, is solely designed to be a simple tool to assist in compliance with the REUSE recommendations.
To install reuse, you need to have the following pieces of software on your computer:
You then only need to run the following command:
pip3 install --user fsfe-reuse
After this, make sure that
~/.local/bin is in your
There are packages available for easy install on some operating systems. You are welcome to help us package this tool for more distributions!
You can also install this tool from the source code, but we recommend the methods above for easier and more stable updates. Please make sure the requirements for the installation via pip are present on your machine.
python3 setup.py install
First, read the REUSE tutorial. In a nutshell:
SPDX-License-Identifier: GPL-3.0-or-later, and
SPDX-FileCopyrightText: $YEAR $NAME. You can be flexible with the format, just make sure that the line starts with
To check against the recommendations, use
~/Projects/reuse-tool $ reuse lint [...] Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
This tool can do various more things, detailed in the documentation. Here a short summary:
addheader --- Add copyright and/or licensing information to the header of a
download --- Download the specified license into the
init --- Set up the project for REUSE compliance.
lint --- Verify the project for REUSE compliance.
spdx --- Generate an SPDX Document of all files in the project.
REUSE is simple to include in CI/CD processes. This way, you can check for REUSE compliance for each build. In our resources for developers you can learn how to integrate the REUSE tool in Drone, Travis, or GitLab CI.
fsfe/reuse Docker image available on Docker
Hub, you can run the helper tool
simply by executing
reuse lint. To use the tool on your computer, you can
mount your project directory and run
reuse lint <path/to/directory>.
Starting local development is very simple, just execute the following commands:
git clone email@example.com:fsfe/reuse-tool.git cd reuse-tool/ python3 -mvenv venv source venv/bin/activate make develop
You need to run
make develop at least once to set up the virtualenv.
make help to see the available interactions.
Copyright © 2017-2019 Free Software Foundation Europe e.V.
This work is licensed under multiple licences. Because keeping this section up-to-date is challenging, here is a brief summary as of July 2019:
For more accurate information, check the individual files.