Skip to content

Rewrite the COPYRIGHT file #39897

Closed
Closed
@brson

Description

@brson
Contributor

This file may be more misleading than not at this point. It has not been kept up to date. I'm not sure the best thing to do here, but maintenance needs to be a concern, particularly now that the flow of crates into tree is opened. Listing the license of every single thing in tree is too hard for humans to do manually.

Activity

xen0n

xen0n commented on Feb 17, 2017

@xen0n
Contributor

Something like the NOTICE aggregation system used by AOSP should be OK. But keeping things synced in-tree may become a problem as the system generates the result NOTICE at build-time.

added
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and tools
and removed
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and tools
on Mar 10, 2017
steveklabnik

steveklabnik commented on Mar 15, 2017

@steveklabnik
Member

docs team triage: tagging p-medium

added
T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
on Jun 14, 2017
added
C-feature-requestCategory: A feature request, i.e: not implemented / a PR.
and removed
T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
on Jul 27, 2017
frewsxcv

frewsxcv commented on Aug 15, 2017

@frewsxcv
Member

Some changes to COPYRIGHT were done in #43498

hsivonen

hsivonen commented on Mar 9, 2018

@hsivonen
Member

It would be useful for people who ship compiler output but who don't ship the compiler with the output if the COPYRIGHT file clearly distinguished between licenses that apply to the compiler and licenses that apply to compiler output.

For the latter case, it would also be useful to characterize under what condition certain licenses apply to the compiler output. One would hope the if jemalloc is disabled, the jemalloc license doesn't apply and if compiling with panic=abort, the libbacktrace license doesn't apply. #48370 suggests this might not be as simple as one could imagine, though, which makes documenting it even more valuable to people who ship compiler output.

14 remaining items

Loading
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-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsA-licensingArea: Compiler licensingC-feature-requestCategory: A feature request, i.e: not implemented / a PR.P-mediumMedium priorityT-coreRelevant to the core team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @steveklabnik@kennytm@brson@carols10cents@frewsxcv

        Issue actions

          Rewrite the COPYRIGHT file · Issue #39897 · rust-lang/rust