Skip to content
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

Rewrite the COPYRIGHT file #39897

Closed
brson opened this issue Feb 17, 2017 · 11 comments
Closed

Rewrite the COPYRIGHT file #39897

brson opened this issue Feb 17, 2017 · 11 comments
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools A-licensing Area: Compiler licensing C-feature-request Category: A feature request, i.e: not implemented / a PR. P-medium Medium priority T-core Relevant to the core team, which will review and decide on the PR/issue.

Comments

@brson
Copy link
Contributor

brson commented Feb 17, 2017

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.

@brson brson added the A-docs label Feb 17, 2017
@xen0n
Copy link
Contributor

xen0n commented Feb 17, 2017

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.

@steveklabnik steveklabnik added A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools P-medium Medium priority and removed A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools labels Mar 10, 2017
@steveklabnik
Copy link
Member

docs team triage: tagging p-medium

@Mark-Simulacrum Mark-Simulacrum added the T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. label Jun 14, 2017
@Mark-Simulacrum Mark-Simulacrum added C-feature-request Category: A feature request, i.e: not implemented / a PR. and removed T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Jul 27, 2017
@frewsxcv
Copy link
Member

Some changes to COPYRIGHT were done in #43498

@hsivonen
Copy link
Member

hsivonen commented Mar 9, 2018

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.

@BubbaSheen
Copy link

I really like the way you explained this. Extremely useful information.

@steveklabnik
Copy link
Member

Triage: it's not clear to me what purpose COPYRIGHT serves, and what its requirements are, so it's hard to know what to do here. Some clarity from @rust-lang/core would be good.

@kennytm kennytm added the T-core Relevant to the core team, which will review and decide on the PR/issue. label Jan 10, 2019
@DevQps
Copy link
Contributor

DevQps commented Apr 5, 2019

@rust-lang/core Could you maybe give us some clarity on the purpose of the COPYRIGHT file such that we can solve this issue?

@DevQps
Copy link
Contributor

DevQps commented Aug 8, 2019

@steveklabnik You're the only one I know that I can ask this :) Do you know who we can ping directly to get input for this so that we can fix the issue?

@carols10cents
Copy link
Member

I am going to add this to the core team triage agenda so that we work on getting legal advice on this.

@DevQps
Copy link
Contributor

DevQps commented Aug 9, 2019

@carols10cents Thanks!

Let us know when there's something we can do :)

@Dylan-DPC
Copy link
Member

closing this as the council issue should be good enough to keep track of this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools A-licensing Area: Compiler licensing C-feature-request Category: A feature request, i.e: not implemented / a PR. P-medium Medium priority T-core Relevant to the core team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests