aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorнаб <nabijaczleweli@nabijaczleweli.xyz>2023-10-04 16:27:40 +0200
committerDrew DeVault <sir@cmpwn.com>2023-10-24 12:27:28 +0200
commit67c1822bca2462c56852ada9e0ff21a546088ee2 (patch)
tree755d0d10848efc233053f01ec2d36c7060d0cbc4
parent03f73a68be27c404065965e3e9ae7782168497f6 (diff)
downloadsr.ht-docs-67c1822bca2462c56852ada9e0ff21a546088ee2.tar.gz
Recommend the REUSE v3 mechanism
-rw-r--r--git.sr.ht/index.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/git.sr.ht/index.md b/git.sr.ht/index.md
index 0427e31..e69280e 100644
--- a/git.sr.ht/index.md
+++ b/git.sr.ht/index.md
@@ -342,6 +342,17 @@ If your project has more than one license, your license file should explain what
licenses apply to what parts of the code in plain English, and include the text
of all applicable licenses.
+For cases like this, the git.sr.ht web UI supports
+version 3.0 of the [REUSE Specfication](https://reuse.software/spec/):
+
+If you include your licences as files matching the pattern
+`LICENSES/$SPDX.$suffix`, where `$SPDX` is the
+[SPDX identifier](https://spdx.org/licenses/) for the licence
+and `$suffix` is any string without a dot,
+the licences will be enumerated in the repo summary
+and `/licenses` pages, alongside a short description and links
+to their corresponding entries on SPDX.org.
+
## Setting a custom README
By default, if found, a `README` plaintext or `README.md` markdown file