(Apache-2.0 OR MIT) explanation page

Hi Rust folk,

I recently open-sourced over 100 of my & my orgs repositories under the (Apache-2.0) OR MIT multi-license.

Starting to add shields also:

But people tend to link them to:
https://opensource.org/licenses/Apache-2.0

Maybe rust-forge is the right place to have an explanation of the multi-license? - Then we can also petition GitHub to include SPDY expression parsing into their license inference system.

Some ideas on what to include on the page:

• https://mail.mozilla.org/pipermail/rust-dev/2012-November/002664.html
• https://internals.rust-lang.org/t/rationale-of-apache-dual-licensing/8952/2
• https://doc.rust-lang.org/1.6.0/complement-project-faq.html#why-dual-mitasl2-license
• https://rust-lang-nursery.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive

There's also a broken link from https://rust-lang-nursery.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive to https://www.rust-lang.org/en-US/faq.html#why-a-dual-mit-asl2-license

Some ideas on the permalink:

• https://forge.rust-lang.org/license
• https://forge.rust-lang.org/license/Apache–2.0-OR-MIT
• https://www.rust-lang.org/license
• https://www.rust-lang.org/license/Apache–2.0-OR-MIT

Review the proposed license references and the broken link from the API Guidelines page, then inspect the rust-forge documentation structure to determine where an explanation page could live. Compare the suggested permalinks and source material, and consider the work done when the page explains the Apache-2.0 OR MIT license and the outdated link is corrected.