-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for tracking licensing metadata with REUSE #99414
Comments
There is a problem right now when running REUSE with the |
One caution I want to raise about REUSE is that they currently recommend uncopyrightable files to be listed as CC0, but Fedora Legal is planning to reclassify CC0 as "not allowed" for code, only "allowed-content". |
…Simulacrum Initial implementation of REUSE This PR implements the first two steps of rust-lang#99414 by: * Adding some scaffolding for REUSE. The `.reuse/dep5` file now marks every file as the custom "TODO" license, which I'll remove in a future PR once Debian imports their metadata. The TODO license is needed so that `reuse lint` works. * Runs `reuse lint` in CI, in the `mingw-check` builder. REUSE currently has a bug when parsing some files in the LLVM source code. This means REUSE will fail when running it in source tarballs of rustc, and that bug prevents us from passing the `--include-submodules` flag in CI. I opened fsfe/reuse-tool#560 upstream with a fix, and as soon as it's merged/released I planned to bump the pinned version to include the fix we need. r? `@Mark-Simulacrum`
The metadata maintained in the Debian package (in the past few years, mostly by me) is valid only for a particular version of the Debian package, currently 1.60/1.61 from 4-5 months ago. It does not apply to current rust git master. Hopefully whoever owns this issue has the next two steps (Enhance.. & Automatically include..) lined up for soon, otherwise the imported metadata will become more and more wrong as time goes by. We also specifically exclude a LOT of stuff from the Debian rust package, one of the reasons being convenience, so that we don't have to maintain the licensing metadata for it. These are listed in the imported file under the very large Files-Excluded section near the top, and includes things like mdbook, llvm, cargo, and various binary blobs. In other words, the licensing metadata imported from Debian is incomplete for the purposes of rust itself, assuming this issue is to fully-document the licensing of the rustc source tarball which pulls in stuff external to this main rust.git repo. |
@infinity0 thanks for the comment! Indeed I know the metadata imported from Debian is incomplete, and I plan to work in the coming weeks to improve it, after which I plan to ask the foundation for help with a legal review of the metadata. I've just been surprisingly busy in the past couple of months :( |
Added a list of REUSE issues I'm tracking in the issue body. |
Draft PR with more licensing annotations is open at: #104527 |
REUSE 4.0.0 is now out, which adds |
#133461 will:
|
This is a tracking issue for MCP 519: track licensing metadata with REUSE
Steps
COPYRIGHT
file and issues labeledA-licensing
.REUSE.toml
#127361collector/compile-benchmarks
rustc-perf#1939.reuse/dep5
in rustbuild.LICENSE-MIT
andLICENSE-APACHE
.src/librustdoc/html/static/COPYRIGHT.txt
COPYRIGHT
in source distributions and tarballsCOPYRIGHT
to explain we're using REUSE and instructions on how to lookup actual metadata.Implementation history
COPYRIGHT
from REUSE metadata #104439reuse
look inside git submodules #118445The text was updated successfully, but these errors were encountered: