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

Restore copyright notice to MIT License #2942

Conversation

CraigMacomber
Copy link

This reverts the removal of the copyright notice from LICENSE-MIT which was done in 22badf1
The notice is part of the MIT license. Since the body text of the license refers to the copyright notice, it is unclear how to conform with the license when redistributing parts of 'THE SOFTWARE' unless it is included here.

This reverts the removal of the copyright notice from LICENSE-MIT which was done in 22badf1
Since the body text of the license refers to the copyright notice, it is unclear how to conform with the license when redistributing parts of 'THE SOFTWARE' unless it is included here.
@kennytm kennytm added not-rfc For PRs that fix things like spelling mistakes, wrong file names, etc. T-core Relevant to the core team, which will review and decide on the RFC. labels Jun 5, 2020
@joshtriplett
Copy link
Member

joshtriplett commented Jun 29, 2020

This was discussed at the time. The requirement in the MIT license to preserve the copyright notice means to preserve the copyright notice that's present; if there's none present, that requirement is trivially satisfied. (Note that in some ways the requirement as stated in the MIT license is just restating copyright law, insofar as you're already legally required to preserve copyright notices.) There's no legal or procedural issue here.

See rust-lang/rust#43498 , which has much more discussion.

Is there some specific problem or concern here motivating this proposal?

@CraigMacomber
Copy link
Author

CraigMacomber commented Jul 8, 2020

Is there some specific problem or concern here motivating this proposal?

I'm using some of the content from this repo in an external location with has different default licensing. (My team at Microsoft is adopting a fork of Rust's RFC process internally), and I want to make sure I properly attribute our modified copy of the template file (which I consider to be "substantial portions of the Software").

Anyway, given the thread you have linked (Thanks, thats very useful), its clear this was not a mistake and is apparently legally well formed, so no more action is needed on the Rust side here. I'll close this PR now as it is unnecessary and apparently incorrect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-rfc For PRs that fix things like spelling mistakes, wrong file names, etc. T-core Relevant to the core team, which will review and decide on the RFC.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants