reuse-docs
reuse-docs copied to clipboard
fsfe
REUSE recommendations, tutorials, FAQ and specification
The instructions say: https://github.com/fsfe/reuse-docs/blob/0913b0a83b36c161966be1c5e70c81bdadfb8a69/spec.md?plain=1#L176-L177 but in the example only one of the two tags has the "Snippet": https://github.com/fsfe/reuse-docs/blob/0913b0a83b36c161966be1c5e70c81bdadfb8a69/spec.md?plain=1#L182-L184 Why doesn't the `License-Identifier` need a prepended `Snippet`?
I'm creating a single PR for this because most changes were already pushed in separate PRs. This PR contains clean-ups and fixes before we can formally release 3.2. Fixes https://github.com/fsfe/reuse-tool/issues/868...
Update deprecated subcommands. `$ reuse addheader` is removed from version 3.0.1 of the tool and should not be included in the tutorial anymore.
Updated deprecated commands with their new equivalents: - `reuse addheader` -> `reuse annotate` - `--explicit-license` -> `--force-dot-license`
Some (mostly content) licenses either directly ask for or encourage, for the origin of the licensed material. To quote from CC-BY-4.0, which is then repeat throughout all of CC licenses...
I'd been pondering this a little while. Famously, the CC0-1.0 licence is not approved by the OSI. It's not disapproved either—it exists in a weird uncomfortable state where the OSI...
Raised in https://github.com/fsfe/reuse-tool/issues/881#issuecomment-1862780188
The FAQ says: https://github.com/fsfe/reuse-docs/blob/0913b0a83b36c161966be1c5e70c81bdadfb8a69/faq.md?plain=1#L544-L555 It is entirely unclear what is meant by "as such". Does it mean: 1. the file must be in the LICENSES directory 2. the file must...
I haven't checked yet whether we already have an FAQ item for this. It would be really good to have instructions/thoughts on using DEP5 to declare the licensing of directories...
Let's finish this after #133 is merged.