From 7e28ef07e70f7f4f6f3662a34a85a8d82a809e16 Mon Sep 17 00:00:00 2001 From: Carmen Bianca BAKKER Date: Mon, 8 Jul 2024 12:16:21 +0200 Subject: [PATCH] More lenience for COPYING and LICENSE-like files Signed-off-by: Carmen Bianca BAKKER --- CHANGELOG.md | 4 ++++ site/content/en/spec-3.3.md | 12 +++++++----- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 566f8c1..b120c50 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -44,6 +44,10 @@ This is the change log for the REUSE Specification. ### Changed +- Also allow `COPYING` and `LICENSE` files to have a suffix with a dash (e.g. + `LICENSE-MIT`). +- The `LICENSE` file may also be spelt `LICENCE`. + ### Deprecated ### Removed diff --git a/site/content/en/spec-3.3.md b/site/content/en/spec-3.3.md index 3c9fb0b..3e2ba5c 100644 --- a/site/content/en/spec-3.3.md +++ b/site/content/en/spec-3.3.md @@ -69,7 +69,9 @@ Covered Files are any file which must contain Licensing Information. This is equal to all files in a project, with the exception of: - The License Files stored in the `LICENSES/` directory. -- `COPYING` and `LICENSE`, with or without file extensions. +- `COPYING`, `LICENSE`, and `LICENCE`, with or without file extensions. These + MAY also contain a dash separator, like `LICENSE-MIT`. These files SHOULD be + in the root of the Project. - The files belonging to the Project's version control system (example: `.git/`). - The files ignored by the version control system (example: files listed in @@ -113,10 +115,10 @@ exception that is part of any SPDX License Expression in any Licensing Information associated with any Covered File, there MUST exist a License File as defined in this section. -You MAY include a `COPYING` or `LICENSE` file (with or without file extensions) -in your project for compliance with other standards, conventions, or tools. -These files MAY contain a copy of the license text, a summary of your licensing, -or anything else. These files are ignored by the REUSE Tool. +You MAY include `COPYING` or `LICENSE` files in your project for compliance with +other standards, conventions, or tools. These files MAY contain a copy of the +license text, a summary of your licensing, or anything else. These files are +ignored by the REUSE Tool. ## Licensing Information