License under dual MIT/Apache-2.0

[carllerche]

The repository currently does not have an associated license, preventing some from contributing.

In order to fully relicense this repository, all contributors must sign-off.

You are receiving this notification because you have contributed to this repo.

While smaller changes can't be copyrighted by law, its non-trivial to find out with certainty 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!

• @alexcrichton
• @aturon
• @carllerche
• @nelsonjchen
• @hockeybuggy
• @rbalicki2
• @shepmaster
• @RadicalZephyr
• @munckymagik
• @khaledkbadr
• @funkill
• @Rufflewind
• @vi
• @mbrubeck
• @radupopescu
• @irtefa
• @SuperFluffy
• @theduke
• @phrohdoh
• @tafia
• @sheeldotme
• @kanerogers
• @braddunbar
• @lazyval
• @toddWannaCode
• @oconnor663
• @mohammadsamir
• @hngnaig
• @DirkyJerky
• @mayhewj
• @jasondavies
• @DmitryBochkarev
• @zmanian
• @baloo
• @schleumer
• @jbendig
• @mre
• @dfockler
• @ineol
• @daschl
• @srijs
• @Freyskeyd
• @danobi
• @kw217
• @AaronStGeorge
• @jedisct1
• @CrockAgile
• @tanimoto
• @awelkie
• @matematikaadit
• @rofrol
• @jefflembeck
• @mquandalle
• @iamcodemaker
• @zklapow
• @schuster
• @acobster
• @cgwalters
• @P-E-Meunier
• @mgattozzi
• @steveklabnik
• @dwrensha
• @redaready

[carllerche]

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

[jasondavies]

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

[hockeybuggy]

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

[khaledkbadr]

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

[phrohdoh]

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

[oconnor663]

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

[schleumer]

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

[radupopescu]

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

[justinmayhew]

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

[SuperFluffy]

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

[nelsonjchen]

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

[srijs]

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

…

On Fri, Feb 16, 2018, at 8:32 AM, Carl Lerche wrote: The repository currently does not have an associated license, [preventing] some from contributing. [preventing]: #124 In order to fully relicense this repository, all contributors must sign-off.> You are receiving this notification because you have contributed to this repo.> While smaller changes can't be copyrighted by law, its non-trivial to> find out with certainty 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! * [ ] @alexcrichton * [ ] @aturon * [ ] @carllerche * [ ] @nelsonjchen * [ ] @hockeybuggy * [ ] @rbalicki2 * [ ] @shepmaster * [ ] @RadicalZephyr * [ ] @munckymagik * [ ] @khaledkbadr * [ ] @funkill * [ ] @Rufflewind * [ ] @vi * [ ] @mbrubeck * [ ] @radupopescu * [ ] @irtefa * [ ] @SuperFluffy * [ ] @theduke * [ ] @phrohdoh * [ ] @tafia * [ ] @sheeldotme * [ ] @kanerogers * [ ] @braddunbar * [ ] @lazyval * [ ] @toddWannaCode * [ ] @oconnor663 * [ ] @mohammadsamir * [ ] @hngnaig * [ ] @DirkyJerky * [ ] @mayhewj * [ ] @jasondavies * [ ] @DmitryBochkarev * [ ] @zmanian * [ ] @baloo * [ ] @schleumer * [ ] @jbendig * [ ] @mre * [ ] @dfockler * [ ] @ineol * [ ] @daschl * [ ] @srijs * [ ] @Freyskeyd * [ ] @danobi * [ ] @kw217 * [ ] @AaronStGeorge * [ ] @jedisct1 * [ ] @CrockAgile * [ ] @tanimoto * [ ] @awelkie * [ ] @matematikaadit * [ ] @rofrol * [ ] @jefflembeck * [ ] @mquandalle * [ ] @iamcodemaker * [ ] @zklapow * [ ] @schuster * [ ] @acobster * [ ] @cgwalters * [ ] @P-E-Meunier * [ ] @mgattozzi * [ ] @steveklabnik * [ ] @dwrensha * [ ] @redaready -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #139

[zmanian]

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

[shepmaster]

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

[ineol]

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

[mre]

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

[aturon]

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

[kw217]

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

[kanerogers]

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

…

On Fri, 16 Feb 2018, 8:57 AM Keith Wansbrough ***@***.***> 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 <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB7b56fQAxwdXhGwSMm1XJKGoRO-afFTks5tVKhTgaJpZM4SHiWa> .

[vi]

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

[AaronStGeorge]

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

[CrockAgile]

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

[theduke]

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

[RadicalZephyr]

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

[mbrubeck]

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

[tanimoto]

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 chose either at their option.

[tafia]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. On Feb 16, 2018 10:48, "Phil Ruffwind" <notifications@github.com> 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 <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHAszpnjSdCY0lVtmeMosL-CztTbYxmuks5tVOxtgaJpZM4SHiWa> .

[DmitryBochkarev]

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

[DirkyJerky]

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

…

On Feb 15, 2018 3:32 PM, "Carl Lerche" ***@***.***> wrote: The repository currently does not have an associated license, preventing <#124> some from contributing. In order to fully relicense this repository, all contributors must sign-off. You are receiving this notification because you have contributed to this repo. While smaller changes can't be copyrighted by law, its non-trivial to find out with certainty 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! - @alexcrichton <https://github.com/alexcrichton> - @aturon <https://github.com/aturon> - @carllerche <https://github.com/carllerche> - @nelsonjchen <https://github.com/nelsonjchen> - @hockeybuggy <https://github.com/hockeybuggy> - @rbalicki2 <https://github.com/rbalicki2> - @shepmaster <https://github.com/shepmaster> - @RadicalZephyr <https://github.com/radicalzephyr> - @munckymagik <https://github.com/munckymagik> - @khaledkbadr <https://github.com/khaledkbadr> - @funkill <https://github.com/funkill> - @Rufflewind <https://github.com/rufflewind> - @vi <https://github.com/vi> - @mbrubeck <https://github.com/mbrubeck> - @radupopescu <https://github.com/radupopescu> - @irtefa <https://github.com/irtefa> - @SuperFluffy <https://github.com/superfluffy> - @theduke <https://github.com/theduke> - @phrohdoh <https://github.com/phrohdoh> - @tafia <https://github.com/tafia> - @sheeldotme <https://github.com/sheeldotme> - @kanerogers <https://github.com/kanerogers> - @braddunbar <https://github.com/braddunbar> - @lazyval <https://github.com/lazyval> - @toddWannaCode <https://github.com/toddwannacode> - @oconnor663 <https://github.com/oconnor663> - @mohammadsamir <https://github.com/mohammadsamir> - @hngnaig <https://github.com/hngnaig> - @DirkyJerky <https://github.com/dirkyjerky> - @mayhewj <https://github.com/mayhewj> - @jasondavies <https://github.com/jasondavies> - @DmitryBochkarev <https://github.com/dmitrybochkarev> - @zmanian <https://github.com/zmanian> - @baloo <https://github.com/baloo> - @schleumer <https://github.com/schleumer> - @jbendig <https://github.com/jbendig> - @mre <https://github.com/mre> - @dfockler <https://github.com/dfockler> - @ineol <https://github.com/ineol> - @daschl <https://github.com/daschl> - @srijs <https://github.com/srijs> - @Freyskeyd <https://github.com/freyskeyd> - @danobi <https://github.com/danobi> - @kw217 <https://github.com/kw217> - @AaronStGeorge <https://github.com/aaronstgeorge> - @jedisct1 <https://github.com/jedisct1> - @CrockAgile <https://github.com/crockagile> - @tanimoto <https://github.com/tanimoto> - @awelkie <https://github.com/awelkie> - @matematikaadit <https://github.com/matematikaadit> - @rofrol - @jefflembeck - @mquandalle - @iamcodemaker - @zklapow - @schuster - @acobster - @cgwalters - @p-e-meunier - @mgattozzi - @steveklabnik - @dwrensha - @redaready — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#139>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE3SYg5zqjHYEK20i4iIQhyi-WAMWPjUks5tVKJfgaJpZM4SHiWa> .

[funkill]

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

[daschl]

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

[Freyskeyd]

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

[awelkie]

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

[irtefa]

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

…

On Fri, Feb 16, 2018 at 8:08 AM Allen Welkie ***@***.***> 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 <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABFlh3Jf0uqdQdllfyKGV2TLniWdgRjcks5tVYvsgaJpZM4SHiWa> .

[dfockler]

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

[danobi]

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

[matematikaadit]

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

[jbendig]

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

[baloo]

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

[mohammadsamir]

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

[rbalicki2]

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

…

On Thu, Feb 22, 2018 at 4:20 AM, msamir ***@***.***> 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 <#139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEFDVZNyfMZ4La98AuPRmCHaV1qmoSCvks5tXTFZgaJpZM4SHiWa> .

[alexcrichton]

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

[dwrensha]

Word.

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

[jedisct1]

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

[steveklabnik]

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

[carllerche]

Ping!

@munckymagik @radupopescu @sheeldotme @braddunbar @lazyval @toddWannaCode @hngnaig @rofrol @jefflembeck @mquandalle @iamcodemaker @zklapow @schuster @acobster @cgwalters @P-E-Meunier @mgattozzi @redaready

[cgwalters]

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

[jefflembeck]

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

[radupopescu]

Hi,
I replied 20 days ago.
Cheers,

[acobster]

Sounds good to me! :)

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

[iamcodemaker]

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

[mgattozzi]

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.

[redaready]

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

[P-E-Meunier]

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

[mquandalle]

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

[carllerche]

@radupopescu Woops, sorry about that. Got you this time!

[rofrol]

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

[radupopescu]

@carllerche No worries! Cheers!

[zklapow]

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

[carllerche]

Ping: @munckymagik @sheeldotme @braddunbar @lazyval @toddWannaCode @hngnaig

[tobz]

Roll call! @munckymagik @sheeldotme @braddunbar @lazyval @toddWannaCode @hngnaig

[sheeldotme]

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

[carllerche]

Authors for all existing content on master have been covered by this issue. As such, I will close. Thanks all.