Skip to content

Tracking issue for tracking licensing metadata with REUSE #99414

Open

Description

@emilyalbini

This is a tracking issue for MCP 519: track licensing metadata with REUSE

Steps

Implementation history

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    A-licensingArea: Compiler licensing
    on Jul 18, 2022
  2. emilyalbini commented on Jul 18, 2022

    @emilyalbini
    MemberAuthor

    There is a problem right now when running REUSE with the --include-submodules flag in our repository (which we'll eventually want to do), as REUSE doesn't handle the formatting of some LLVM comments. Opened fsfe/reuse-tool#560 to fix that issue.

  3. cuviper commented on Aug 8, 2022

    @cuviper
    Member

    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".

    https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/YUQJHPX6EC2RGXUM7VCKXKWNW6W7DKS6/

  4. added a commit that references this issue on Aug 20, 2022
  5. infinity0 commented on Sep 23, 2022

    @infinity0
    Contributor

    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.

  6. emilyalbini commented on Sep 26, 2022

    @emilyalbini
    MemberAuthor

    @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 :(

  7. emilyalbini commented on Nov 10, 2022

    @emilyalbini
    MemberAuthor

    Added a list of REUSE issues I'm tracking in the issue body.

  8. emilyalbini commented on Nov 17, 2022

    @emilyalbini
    MemberAuthor

    Draft PR with more licensing annotations is open at: #104527

  9. emilyalbini commented on Jul 5, 2024

    @emilyalbini
    MemberAuthor

    REUSE 4.0.0 is now out, which adds REUSE.toml. That file fixes all of the concerns we had with REUSE, and I thus opened #127361 to migrate to it. rust-lang/rustc-perf#1939 is also something we should do to make our annotations more accurate.

  10. jonathanpallant commented on Nov 29, 2024

    @jonathanpallant
    Contributor

    #133461 will:

    • Remove LICENSE-MIT and LICENSE-APACHE.
    • Replace COPYRIGHT to explain we're using REUSE and instructions on how to lookup actual metadata.
    • Auto-generate COPYRIGHT in source distributions and tarballs (it's COPYRIGHT.html and COPYRIGHT-library.html)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-licensingArea: Compiler licensingC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions