GitLab

described here: https://github.com/ipfs/team-mgmt/issues/849

This series of commits aims to update go-ipfs to follow a dual-licensing best practice based on research into open-source licensing by @ianjdarrow. He recommends a dual MIT and Apache 2.0 license -

> This has two major benefits:

> - There are concerns in the open source community about whether the MIT license leaves users vulnerable to patent infringement claims. We think the pure legal risk is small, but the way the open source community interacts with our project is really important. It makes sense to pick the license that makes the largest number of people comfortable.
- There's now no reason to adopt a separate DCO, since the Apache-2 license grant addresses the same issue.

> Why use a dual license, instead of just Apache-2? The Apache-2 license is incompatible with the GPLv2 license, which includes things like the Linux kernel. With a dual license, GPLv2 projects can just use the MIT license instead. Our goal is to make our software available to as many projects as possible, so we'd rather adopt a licensing scheme that doesn't exclude anyone.

In addition to these commits, we also need to get an explicit OK from current and past contributors to give their consent to relicensing - which will happen in an issue thread.

See https://github.com/ipfs/go-ipfs/pull/2883#issuecomment-227528997

License: MIT
Signed-off-by: Richard Littauer <richard.littauer@gmail.com>

See https://github.com/ipfs/community/issues/124

License: MIT
Signed-off-by: Richard Littauer <richard.littauer@gmail.com>