Skip to content

Commit

Permalink
Make requirements apply to the same set of files (fsfe#85)
Browse files Browse the repository at this point in the history
Signed-off-by: Carmen Bianca BAKKER <carmenbianca@fsfe.org>
  • Loading branch information
Jayman2000 authored and carmenbianca committed May 21, 2024
1 parent d772f28 commit 7b0c40d
Showing 1 changed file with 17 additions and 21 deletions.
38 changes: 17 additions & 21 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,9 @@ log](https://git.fsfe.org/reuse/docs/src/branch/master/CHANGELOG.md).

These are the definitions for some of the terms used in this specification:

- REUSE Tool --- helper tool for compliance with this Specification; available
at <https://github.com/fsfe/reuse-tool>.

- Project --- any unit of content that can be associated with a distribution of
software. Typically, a Project is composed of one or more files. Also
sometimes called a package.
Expand All @@ -32,6 +35,16 @@ These are the definitions for some of the terms used in this specification:
copyright holders of a file or work, and describes under which licenses the
file or work is made available.

- Covered File --- any file in a Project, except for
- The License Files.
- The files belonging to the Project's version control system (example:
`.git/`).
- The files ignored by the version control system (example: Files listed in
`.gitignore`).
- The files in the `.reuse/` directory in the root of the Project. This
directory MUST contain only files relevant for the operation of the REUSE
Tool.

- SPDX Specification --- SPDX specification, version 2.1; as available on
<https://spdx.org/specifications>.

Expand All @@ -50,13 +63,10 @@ These are the definitions for some of the terms used in this specification:
Specification takes precedence. Specifically in the case of the `Copyright`
and `License` tags.

- REUSE Tool --- helper tool for compliance with this Specification; available
at <https://github.com/fsfe/reuse-tool>.

## License Files

A Project MUST include a License File for every license under which files in the
Project are licensed.
A Project MUST include a License File for every license under which Covered
Files are licensed.

Each License File MUST be placed in the `LICENSES/` directory in the root of
the Project. The name of the License File MUST be the SPDX License Identifier of the
Expand All @@ -75,22 +85,8 @@ exception that does not exist in the SPDX License List.

## Copyright and Licensing Information

Each file in the Project MUST have Copyright and Licensing Information
associated with it, except the following files:

- The License Files.

- The files belonging to the Project's version control system (example:
`.git/`).

- The files ignored by the version control system (example: Files listed in
`.gitignore`).

- The files in the `.reuse/` directory in the root of the Project. This
directory MUST contain only files relevant for the operation of the REUSE
Tool.

There are two ways to associate Copyright and Licensing Information with a
Each Covered File MUST have Copyright and Licensing Information associated with
it. There are two ways to associate Copyright and Licensing Information with a
file.

### Comment headers
Expand Down

0 comments on commit 7b0c40d

Please sign in to comment.