License the whole rustc-perf repository under the MIT license

[Kobzol]

This repository currently does not have a top-level LICENSE file (#1880), which means that not all of its code is covered by a license.
We would like to license the whole rustc-perf repository (apart from the collector/compile-benchmarks directory, which has its own licenses) under the MIT License, to make it easier to use rustc-perf in rustc source distributions. In the future, we might want to extend this license to MIT/Apache 2.0 (although currently we're aiming at MIT, as a start, since it is easier), hence we would like to ask the contributors to agree with a dual MIT/Apache 2.0 license, as a sort of future-proofing.

To do that, we need contributors that made commits to this repository (with some caveats, see below) to agree by posting a comment stating their approval to this issue. Please see instructions at the bottom of this issue if you are mentioned in the list below. I will try to also contact the contributors individually.

How did we select the list of contributors from whom we need the approval?

I analyzed the commits from rustc-perf going all the way back to e99853d4777a1df001853c619eead0c891c28488. In this commit, there was a top-level MIT license at the root of the repository, therefore all earlier commits should be MIT licensed. Then I found a set of contributors that made at least a single commit to any other directory than collector and site, because these two were already MIT licensed.

I used this script for performing the analysis.

Related issues: #1880, #1927
PR with the new license: #1881

Checkoff

To agree to the licensing terms, please comment with the following text on this issue (you can copy the text using the copy button on the right):

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

Thank you very much!

Affected contributors:

• @Mark-Simulacrum
• @Kobzol
• @rylev
• @nnethercote
• @pnkfelix
• @klensy
• @tgnottingham
• @ecstatic-morse
• @jyn514
• @wesleywiser
• @s7tya
• @Horki (their code is no longer in this repository)
• @weihanglo
• @homersimpsons
• @eth3lbert
• @pietroalbini
• @chengr4
• @blyxyas
• @miwig
• @kennytm
• @jsha
• @GuillaumeGomez
• @sn99
• @apiraino
• @est31
• @eddyb
• @RalfJung
• @alex
• @ishitatsuyuki
• @alexcrichton
• @SimonSapin

[Kobzol]

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

[GuillaumeGomez]

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

[ishitatsuyuki]

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

[homersimpsons]

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

[s7tya]

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

[blyxyas]

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

[sn99]

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

[kennytm]

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

[weihanglo]

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

[RalfJung]

I license all my past contributions to the rust-lang/rustc-perf repository under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

(I don't think it makes sense for me to make statements about future contributions now, and I don't see how that is relevant for this licensing issue.)

[rylev]

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

[alexcrichton]

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

[alex]

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

[eth3lbert]

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

[pnkfelix]

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

[SimonSapin]

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

[wesleywiser]

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

[klensy]

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

[jsha]

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

[nnethercote]

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

[chengr4]

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

[jyn514]

... good luck.

---

I license all my past contributions to the rust-lang/rustc-perf repository under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[est31]

I license all my past contributions to the rust-lang/rustc-perf repository under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[Mark-Simulacrum]

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

[apiraino]

I think I don't need to make any licensing explicit on my end since my only contribution was a typo fix in a perf. triage report 😄 but anyways

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

[pietroalbini]

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

[miwig]

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

[tgnottingham]

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

[eddyb]

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

[ecstatic-morse]

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

[Kobzol]

So, we got 30/31 approvals in 5 (!) days, that is awesome! Big thanks to everyone who expressed their approval.

The last remaining contributor who didn't express their approval yet, @Horki, contributed code that was since deleted and is no longer a part of this repository. Therefore I think that we should be good with moving forward with the licensing.

[Kobzol]

A top-level MIT license has been added: #1881.