REUSE recommendations, tutorials, FAQ and specification https://reuse.software
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.
Go to file
Max Mehl ba349196b6
Merge pull request #121 from Jayman2000/minor-capitalization-fix
12 hours ago
.reuse make reuse compliant 2 years ago
LICENSES Remove unused license 4 years ago
po add available languages to config 9 months ago
.gitignore make reuse compliant 2 years ago
CHANGELOG.md Bump to v3.0 4 years ago
README.md unify wrapping 9 months ago
faq.md Communicate change from master to main 4 months ago
spec.md Minor capitalization fix 2 days ago
tutorial.md Communicate change from master to main 4 months ago

README.md

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.

Install

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 reuse.software.

Usage

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

Contribute

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

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

Branches

The latest official specification release is in the stable branch, while the main branch (master) contains fixes and new and potentially breaking specification changes. Typically, non-spec changes or insignificant fixes for the spec are "backported" to the stable branch.

License

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