Relicense as MIT/Apache2

[philpax]

The going standard in the Rust ecosystem is MIT/Apache2 for a variety of reasons. Here's Bevy's PR for more context: bevyengine/bevy#2373

I suggest we do this sooner rather than later (we'll need the consent of all contributors)

[setzer22]

No objections with the change 👍

I'll just ping everyone who has merged changes so far to make people aware of this (and sorry all about the ping):

• @KerfuffleV2
• @RoyVorster
• @odysa
• @jempabroni
• @Metalflame12
• @bcho
• @darthdeus
• @trizko
• @mwbryant

[KerfuffleV2]

No objections here. Slightly changed version of the suggested "agreeing to the change" language:

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

[bcho]

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

[Metalflame12]

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

[mwbryant]

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

[trizko]

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

[ghost]

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

[odysa]

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

[darthdeus]

I license all my contributions under whatever license the authors choose at whatever point in time in the future, including but not limited to MIT/Apache-2.0.

[philpax]

@RoyVorster ping

[philpax]

I've been unsuccessful in contacting Roy, but I believe that #125 will more or less replace all of the code he's contributed, so we should be in the clear. Given that, I'll proceed with the relicensing once all of our pending PRs are in.