Relicense bevy_mod_picking under dual MIT/Apache-2.0

[aevyrie]

To agree to this relicense, please read the details in this issue, then leave a comment with the following message:

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

If you disagree, please respond with your reasoning (just don't expect us to change course at this point). Anyone who doesn't agree to the relicense will have any contributions that qualify as "copyrightable" removed or re-implemented.

Why: bevyengine/bevy#2373

What will this look like?

After getting explicit approval from each contributor of copyrightable work
(as not all contributions qualify for copyright, due to not being a "creative
work", e.g. a typo fix), we will add the following file to our README:

License

Licensed under either of

• Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.

We will add LICENSE-{MIT,APACHE} files containing the text of each license. We will also update the license metadata in our Cargo.toml to:

license = "MIT OR Apache-2.0"

[aevyrie]

• @guimcaballero
• @UnFlimFlammable
• @nickan
• @verzuz
• @mockersf
• @BrunoWallner
• @nicbarker
• @RishiKumarRay
• @AltF02
• @Ratysz
• @obsgolem
• @DocDock
• @jakobhellermann
• @mcobzarenco
• @thlorenz
• @crabs-n-simone
• @YoshieraHuang
• @johanhelsing
• @gavlig
• olegomon

[mockersf]

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

[sim-the-bean]

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

[jakobhellermann]

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

[johanhelsing]

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

[AltF02]

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

[Ratysz]

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

[obsgolem]

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

[gavlig]

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

(I specified the project name in text, hope that's alright)

[guimcaballero]

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

[YoshieraHuang]

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

[mcobzarenco]

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

[thlorenz]

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

[BrunoWallner]

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

[RishiKumarRay]

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

[aevyrie]

Re-pinging:
@DocDock
@nicbarker
@nickan
@verzuz
@UnFlimFlammable

[UnFlimFlammable]

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

…

On Thu, Jul 14, 2022 at 5:11 PM Aevyrie ***@***.***> wrote: Re-pinging: @DocDock <https://github.com/docDock> @nicbarker <https://github.com/nicbarker> @nickan <https://github.com/Nickan> @verzuz <https://github.com/verzuz> @UnFlimFlammable <https://github.com/UnFlimFlammable> — Reply to this email directly, view it on GitHub <#138 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABT6CF25FEIA5ET2QH5SC4TVUCGAXANCNFSM5YAD6TRA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[verzuz]

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

[chaoticgood1]

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

[olegomon]

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