REUSE recommendations, tutorials, FAQ and specification
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Max Mehl b40c7fff5d
make reuse compliant
1 week ago
.reuse make reuse compliant 1 week ago
LICENSES Remove unused license 1 year ago
po make reuse compliant 1 week ago
.gitignore make reuse compliant 1 week ago Bump to v3.0 1 year ago use po4a to make all docs translatable on Weblate and others (#61) 1 week ago FAQ: don't link to unwritten MIT/BSD section 1 year ago License Identifier, not Identifier 1 year ago Mention name of license files in tutorial (#64) 3 months ago

REUSE documents

standard-readme compliant REUSE compliant

We’re working to make managing copyrights and licenses in free and open source software easier. This is a collection of tutorials, FAQs and specifications to demonstrate how to add copyright and license information to a project in ways which allow for more automation.


There’s no installation here, only the plain text documents. The sister repository reuse-website includes this repository as a submodule to display it on


Go to and enjoy :-) If your project follows the reuse guidelines, we encourage you to show that in your and similar! Just register your project with the REUSE API and copy the resulting badge code in your README file.


We’d love to get feedback on these practices, ideally in the form of pull requests which we can discuss around.

We also accept and appreciate feedback by creating issues in the project or by sending an e-mail to the public REUSE mailing list.


Translation happens by conversion Markdown into gettext using po4a. To generate the .md files from the gettext .po files, run: po4a po/po4a.conf.


The relevant documents in this repository are licensed under Creative Commons Attribution-ShareAlike 4.0.