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!
- @Aatch
- @aatxe
- @achanda
- @AGWA
- @aidanhs
- @alexcrichton
- @Amanieu
- @AndyGauge
- @aochagavia
- @apasel422
- @apoelstra
- @archshift
- @arielb1
- @ashleygwilliams
- @aturon
- @barosl
- @benaryorg
- @bestouff
- @blaenk
- @brson
- @bsansouci
- @bstrie
- @BurntSushi
- @canndrew
- @cardoe
- @carllerche
- @carols10cents
- @Centril
- @cesarb
- @cgaebel
- @chriskrycho
- @chris-morgan
- @cjwelborn
- @CloudiDust
- @cmr
- @cramertj
- @DerSaidin
- @dgrunwald
- @dhardy
- @Diggsey