Configure REUSE licence markup and config #139
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR configures REUSE license markup and configuration to establish proper license compliance for the project. REUSE is a standard for marking copyright and license information in software projects.
- Adds REUSE.toml configuration file to specify license annotations for different file patterns
- Integrates REUSE license checking into the build process via Makefile
- Includes required license text files for all referenced licenses
Reviewed Changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| REUSE.toml | Configuration file defining license annotations for different file patterns and copyright holders |
| Makefile | Adds REUSE lint check to the existing check target |
| LICENSES/*.txt | Standard license text files for GPL-2.0-or-later, GPL-3.0-only, BSD-3-Clause, BSD-4-Clause, and custom licenses |
| AUTHORS.md | Documentation of project authors and contributors |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
This is in line with /LICENSE which appears to be intended to cover the bulk of the repo (per headers and context and `debian/copyright`)
License taken from /external/geotranz/readme.txt
Taken from https://github.com/libusb/hidapi via /external/hidapi
Based on config in debian/copyright
doismellburning
force-pushed
the
feature/reuse
branch
from
7a7db02 to
863f035
Compare
|
Fixes #86 |
Yay! (Debian Trixie, my local dev machine)
Boo! ( |
(I should probably pin it, but that's a later problem) Debian Trixie (my dev box) ships a `reuse` supporting version 3.3 of the spec, but Ubuntu 24.04 (the latest Ubuntu on GitHub Actions) only supports 3.0 - so let's grab it from PyPI not the OS packages
|
Per the FAQ (https://reuse.software/faq/#bulk-license) I should really have marked up individual source files, and I intend to do that going forwards, but using patterns in the config TOML was a faster and easier way to get to compliance sooner, and I think that was the right priority |
1 participant
No description provided.