[5/7] Relicense under dual MIT / Apache v2

[Manishearth]

This is one of the sub-issues for relicensing this repo to MIT / Apache v2, the license used by most of the Rust ecosystem. For more information, see #3093

To agree to relicensing, comment with :

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

I'll be ticking off the boxes below as people turn up.

(You may wish to unsubscribe from this issue after leaving your comment)

• @EpocSquadron
• @elliottneilclark
• @jedisct1
• @gendx
• @guido4000
• @hdhoang
• @cuviper
• @pythonesque
• @iKevinY
• @mattyhall
• @wafflespeanut
• @rcoh
• @tomprince
• @TomasKralCZ
• @detrumi
• @bestouff
• @zmbush
• @aaudiber
• @DarkEld3r
• @tspiteri
• @aochagavia
• @sourcejedi
• @dashed
• @AVerm
• @andersk
• @afck
• @Baelyk
• @bkchr
• @ogham
• @BenoitZugmeyer

[Baelyk]

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

[sourcejedi]

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

[mattyhall]

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

[andersk]

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

[zmbush]

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

[guido4000]

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

[rcoh]

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

…

On Mon, Aug 27, 2018 at 4:49 PM Guido ***@***.***> 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 <#3098 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAeFZyiLdf07csDvjorONIuNh6rc-Yw5ks5uVIWAgaJpZM4WOnE8> .

[iKevinY]

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

[hdhoang]

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

[wafflespeanut]

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.

[bkchr]

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

[afck]

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

[ogham]

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

[aochagavia]

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

[tspiteri]

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

[bestouff]

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

[BenoitZugmeyer]

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

[stanislav-tkach]

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

[dashed]

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

[AVerm]

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

[cuviper]

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

[elliottneilclark]

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

[detrumi]

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

[to-mas-kral]

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

[tomprince]

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

[mati865]

Pinging @EpocSquadron @gendx @pythonesque @aaudiber

[aaudiber]

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

[pythonesque]

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

[gendx]

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

[Manishearth]

@EpocSquadron only had contributions to the README, to sections which have since been replaced, so marking them as done.

Thank you all for commenting, I'm closing this issue as we got all the comments -- please follow #3093 if you want updates on this.