Auto merge of #43498 - joshtriplett:fix-notices, r=aturon
Copyright/license headers (As discussed with @aturon and @est31. CC @rust-lang/core.) Currently, rust-lang/rust includes notices that say things like ``` The Rust Project is copyright 2010, The Rust Project Developers. ``` or ``` Copyright (c) 2010 The Rust Project Developers ``` or ``` // Copyright 2017 The Rust Project Developers. See the COPYRIGHT // file at the top-level directory of this distribution and at // http://rust-lang.org/COPYRIGHT. ``` These notices aren't accurate. "Copyright YYYY Some Name" has a specific legal meaning, and "The Rust Project Developers" isn't a legal entity. In practice, the actual legal structure is that all Rust contributors retain their copyrights when contributing to Rust, and just license them under MIT/Apache-2.0. Our legal notices should reflect that. This came up because of RFC 2044, which proposed fixing this for the RFC repository. That effort started out by copying the rust-lang/rust notices, propagating this issue. Based on discussion with @aturon, the two of us propose the following: - Delete the per-file notices entirely, for any files licensed under the standard terms. (Keep notices for anything that's *not* MIT/Apache-2.0.) - An alternative to that would be to just delete the first paragraph of the standard notice, and keep the second paragraph that points to the MIT and Apache 2.0 licenses. - Delete the first paragraph of LICENSE-MIT (the inaccurate pseudo-copyright line), leaving only the text of the MIT license. - Edit the COPYRIGHT file to more accurately describe the situation (changing the pseudo-copyright line immediately under "longer version", and editing the text that starts with "additional copyright may be ...", to just always state that copyrights are retained by the Rust contributors, and licensed under MIT/Apache-2.0 (with the exceptions to that explicitly noted in that file). If @rust-lang/core is fine with this proposal, I'd be happy to provide a pull request with the proposed fixes.
Showing
想要评论请 注册 或 登录