This is a tracking issue for RFC 2044 (thread, rendered), to put the rust-lang/rfcs repo under dual MIT/Apache-2 licensing terms.

Necessary steps for execution:

Asking past contributors to agree with the licensing terms (with <=40 contributors each to bypass the github mention limit of 50):

• [1/4] License under dual MIT/Apache-2.0 rfcs#2076
• [2/4] License under dual MIT/Apache-2.0 rfcs#2077
• [3/4] License under dual MIT/Apache-2.0 rfcs#2078
• [4/4] License under dual MIT/Apache-2.0 rfcs#2079

And further:

• PR to rust-lang/rfcs to add LICENSE-MIT and LICENSE-APACHE files, talk about the licensing situation in the README, and edit the template to include the header: Add note of the RFC 2044 licensing process to README and update template rfcs#2075
• Asking first time contributors who opened PRs before the PR above got merged to agree with the terms: Licensing sign off issue for first time contributors rfcs#2096
• PR to rust-lang/rfcs to signify the licensing change is complete. Doable once every (or almost every) contributor has signified consent with the licensing terms. Also, figure out what to do about the contributions by people who didn't give their consent: Remove files with contributions from the people where no approval of the licensing terms was received rfcs#2193