Ninja-edited the syntax after the last pull request broke it.
|2 months ago|
|site||2 months ago|
|.drone.yml||1 year ago|
|Dockerfile||1 year ago|
|LICENSE||1 year ago|
|README.md||9 months ago|
|generate.sh||1 year ago|
|hosts||1 year ago|
|playbook.yml||9 months ago|
We’re working to make managing copyrights and licenses in free and open source software easier. This is the website for a guide of best practices, meant to demonstrate how to add copyright and license information to a project in ways which allow for more automation.
There’s no installation here, but you may try running
hugo in the
site/ directory to generate the website when testing locally.
Typically, we let our Drone CI build and deploy the website for us.
Go to https://reuse.software/ and enjoy :-) If your project follows the reuse
guidelines, we encourage you to show that in your
README.md and similar! Just
copy this badge into your readme:
We’d love to get feedback on these practices, ideally in the form
of pull requests which we can discuss around. To be able to contribute
in this way, you need an account on
git.fsfe.org, which you can
get by going to our account creation page. This will sign you up for a volunteer account with the FSFE.
Once you’ve registered, your account needs to be activated. Just shoot a mail to firstname.lastname@example.org or directly to email@example.com saying you’ve registered and would like to be activated. As soon as your account is activated, you can set a username and proceed to login to
The content of the website, the best practices, are licensed under Creative Commons Attribution-ShareAlike 4.0.