Repository navigation
[2/4] License under dual MIT/Apache-2.0 #2077
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!
- @durka
- @dwijnand
- @eddyb
- @eefriedman
- @eminence
- @Ericson2314
- @est31
- @extesy
- @F001
- @flugsio
- @Fraser999
- @freebroccolo
- @gankro
- @glaebhoerl
- @glebm
- @GuillaumeGomez
- @Havvy
- @Henning-K
- @hunan-rostomyan
- @huonw
- @Hywan
- @IonoclastBrigham
- @iopq
- @ipetkov
- @japaric
- @jethrogb
- @JinShil
- @jonas-schievink
- @jonathandturner
- @joshtriplett
- @kalisjoshua
- @kamalmarhubi
- @kballard
- @Kimundi
- @king6cong
- @kmcallister
- @KodrAus
- @krdln
- @lambda
- @LeoTestard
Activity
eminence 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.
KodrAus 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.
sophiajt 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.
krdln 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.
durka 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.
japaric 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.
est31 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.
jethrogb 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.
hunan-rostomyan 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.
IonoclastBrigham commentedon Jul 25, 2017
lilyball 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.
ipetkov 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.
Gankra 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.
king6cong 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.
flugsio 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.
14 remaining items
kamalmarhubi commentedon Aug 2, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
JinShil commentedon Aug 2, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Gankra commentedon Aug 2, 2017
(note for records: @huonw has contacted the core team and provided his consent in private)
kmcallister commentedon Aug 3, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Hywan commentedon Aug 7, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Ericson2314 commentedon Aug 8, 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:
extesy commentedon Aug 14, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Fraser999 commentedon Aug 15, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
LeoTestard commentedon Oct 29, 2017
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
eminence commentedon Oct 29, 2017
Everyone signed off! 🎉 🎉 👏
est31 commentedon Oct 29, 2017
Everybody: Thank you very much. I can close this issue as resolved then!