MIT/Apache relicensing

[raviqqe]

I'll appreciate that if this crate is relicensed under MIT/Apache as Rust.

[mbrubeck]

I agree.

For those of us who contributed to this crate in our role as Mozilla employees, we'd need Mozilla to sign off on this, which I expect it would be willing to do. @larsbergstrom, is there an established process for requesting this?

We will also need sign-off from all non-employee individual copyright holders. We can contact them if we decide to make this change.

For reference, here is the contribution history of this code before it was moved to this repo:

https://github.com/servo/rust-selectors/blame/e8dd4cfe4d6a40363ca5df468b29121fe25a7956/src/smallvec.rs

https://github.com/servo/servo/blame/d26345f868e4261760ce204bdc383941e8f14621/components/util/smallvec.rs

[larsbergstrom]

@mbrubeck I'll check with legal, but in general for non-strategic code bases it is acceptable to use the predominant license of the community. I'll post back here with yes/no. Thanks for checking with me!

[larsbergstrom]

@mbrubeck Yes, we can do this in the same way as the following:
servo/gleam#57

That is, we list all of the contributors, have each of them sign off on the transfer, and then we can move forward.

[raviqqe]

Any progress or decisions so far? Can I help by doing something?

[cramertj]

Ping @mbrubeck @larsbergstrom can you start start the license change check-off? (as in servo/gleam#57)

[mbrubeck]

Hello! The Servo team would like to make the smallvec Rust crate available under the dual MIT/Apache-2.0 license used by Rust itself and by most open source Rust crates. The smallvec crate is currently published under the Mozilla Public License 2.0, because it was originally part of the servo repo which is under that license.

To change the license, we need permission from all of the copyright holders. If you have contributed code or documentation to this crate, your username should be listed below. If you agree to re-license your contributions, please comment on this issue with the following statement:

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

Below is a list of all the accounts who contributed copyrightable changes to this crate. This includes open PRs, and excludes commits that only contained trivial mechanical changes like version bumps or git merges.

• @AerialX
• @Amanieu
• @arthurprs
• @bluss
• @c0gent
• @cfallin
• @cgaebel
• @chpio
• @cramertj
• @dbkaplun
• @hoggetaylor
• @Marwes
• @mbrubeck
• @Ms2ger
• @nipunn1313
• @pcwalton
• @Pratyush
• @SergioBenitez
• @SimonSapin
• @tomaka
• @Vurich
• @Xaeroxe

[mbrubeck]

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

[chpio]

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

[pcwalton]

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

[cfallin]

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

[arthurprs]

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

[Amanieu]

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

[cramertj]

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

[c0gent]

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

[Marwes]

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

[SimonSapin]

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

[Pratyush]

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

[dbkaplun]

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

[hoggetaylor]

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

[AerialX]

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

[nipunn1313]

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

[bluss]

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

[Ms2ger]

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

[Vurich]

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

[tomaka]

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

[SergioBenitez]

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

[mbrubeck]

@cgaebel's contributions were made as a Mozilla employee, so I believe Mozilla's approval is sufficient in that case. If so, that's everyone. Thank you all!