[3/4] License under dual MIT/Apache-2.0 #2078
Description
This is a sign-off issue as per RFC 2044 (tracking issue) to license the rust-lang/rfcs repo under dual Apache2/MIT licensing terms.
You are receiving this notification because you have contributed to this repo.
For a discussion on why this move is desired, please see the RFC's text.
While smaller changes can't be copyrighted by law, its non-trivial to find out with certainity whether a given change falls under copyright or not, due to the nature of the matter. Therefore I'm asking you to agree to the new terms even if you consider your contributions to be not copyrightable.
To minimize noise in your inbox, let me use this opportunity to ask those among you who have unmerged RFCs in the queue to add a license header to your RFC drafts. In a few days/weeks I'll go through the list of open RFCs and ask for license headers to be added for the remaining RFCs that lack headers. The RFC's text contains the precise header (and has one already itself). Filing PRs to add headers to your already merged RFCs is not required, they will get headers in bulk.
Checkoff
To agree to the licensing terms, please comment with:
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Thank you!
- @lukaramu@P1start
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
Participants
Activity
Manishearth commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
retep998 commentedon Jul 25, 2017
I license past contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. I also allow licensees to choose to be fluffy rabbits.
petrochenkov commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
ranweiler commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
RalfJung commentedon Jul 25, 2017
I license past contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
(I see no reason to cover all my future contributions as well; they will be licensed as I create them. I usually refrain from making legally binding statements covering all my future actions; what do I know what the future brings. Also, if the license of this repository changes again, all my contributions following that hypothetical license change would still also be licensed under MIT/Apache-2.0, which doesn't seem intended.)
mirandadam commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
mirandadam commentedon Jul 25, 2017
Also, i agree with @RalfJung that the statement about future contributions is superfluous, but I made it anyway.
novalis commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
lambda-fairy commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
pthariensflame commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
oli-obk commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
ranma42 commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
pitdicker commentedon Jul 25, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
pythonesque commentedon Jul 25, 2017
I license past contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
22 remaining items
mbrubeck commentedon Jul 31, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
llogiq commentedon Aug 5, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
est31 commentedon Aug 13, 2017
Friendly ping:
pnkfelix commentedon Aug 18, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
o11c commentedon Aug 21, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
mdinger commentedon Aug 29, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Centril commentedon Apr 26, 2018
Triage ping @quantheory
Centril commentedon Oct 8, 2018
Triage ping @quantheory
Dylan-DPC-zz commentedon Dec 23, 2019
@quantheory waiting for you to consent to this
quantheory commentedon Jul 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Kobzol commentedon Jul 26, 2024
Thank you everyone! Now we got the approval from everyone on this list.