Licensing sign off issue for first time contributors

[est31]

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.

For a discussion on why this move is desired, please see the RFC's text.

You are receiving this notification because you have opened a PR to contribute to this repo.

As you have opened your pull request before PR #2075 was merged, which implicitly assumes from any new PR to include content licensed under these conditions, your contribution might be included without you having agreed to the licensing terms. Also, you are a first-time contributor, which means I didn't include you in my earlier sign off issues for past contributors (#2076, #2077, #2078, #2079).

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.

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!

• @Aaronepower
• @ciphergoth
• @clarcharr
• @contactomorph
• @cristicbz
• @cswindle
• @DemiMarie
• @dobkeratops
• @estebank
• @gnzlbg
• @ishitatsuyuki
• @kennytm
• @mgattozzi
• @mitsuhiko
• @Osspial
• @Rufflewind
• @s3bk
• @scalexm
• @schuster
• @semarie
• @skade
• @VFLashM
• @Xaeroxe
• @Zoxc

[ishitatsuyuki]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[XAMPPRocky]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[kennytm]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[gnzlbg]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

…

On Sat 5. Aug 2017 at 13:41, kennytm ***@***.***> wrote: I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2096 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3NpkJDK9MsRKAYotgDfXLqeUQj3S1Sks5sVFTkgaJpZM4OucFd> .

[scalexm]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[Xaeroxe]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[cristicbz]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[mitsuhiko]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[schuster]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[VFLashM]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[clarfonthey]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[Rufflewind]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

[Zoxc]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.