Re-license js-ipfs-http-client to MIT + Apache 2

alanshaw commented 4 years ago

@ianjdarrow has done some research into open-source licensing and determined that dual-licensing as MIT and Apache 2 is a best practice. Quoting from his writing elsewhere:

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.

What we need to do:

The licences are being updated in https://github.com/ipfs/js-ipfs-http-client/pull/1179, the next step is to get an explicit OK from our current and past contributors to consent to the relicensing. To keep track of things, below is a contributor sign-off list. Contributors can either check the box next to their github handle, or comment on this issue thread with the following text:

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

Contributor sign-off:

[x] @daviddias (673)
[x] @alanshaw (215)
[x] @dignifiedquire (153)
[x] @achingbrain (71)
[ ] @jbenet (49)
[ ] @mappum (38)
[ ] @krl (27)
[x] @travisperson (25)
[ ] @hacdias (17)
[ ] @ckeenan (14)
[x] @hugomrdias (14)
[x] @vmx (13)
[ ] @richardschneider (11)
[ ] @harlantwood (11)
[ ] @lidel (10)
[x] @RichardLitt (10)
[x] @noffle (9)
[ ] @victorb (8)
[x] @fbaiodias (7)
[ ] @nginnever (7)
[x] @pgte (5)
[x] @MichaelMure (5)
[x] @vasco-santos (5)
[ ] @magik6k (5)
[ ] @gavinmcdermott (4)
[x] @jacobheun (4)
[x] @olizilla (4)
[x] @dirkmc (4)
[ ] @alexmingoia (3)
[ ] @dryajov (3)
[ ] @Mithgol (3)
[x] @whyrusleeping (3)
[x] @atfornes (2)
[x] @fsdiogo (2)
[ ] @JeffDownie (2)
[ ] @JonKrone (2)
[x] @maxlath (2)
[ ] @niinpatel (2)
[ ] @haadcode (2)
[x] @JGAntunes (2)
[ ] @flipflopsimsommer (1)
[x] @dannyid (1)
[ ] @autonome (1)
[ ] @the-owl (1)
[x] @dostu (1)
[x] @Fil (1)
[x] @filips123 (1)
[ ] @wraithgar (1)
[x] @KrishnaPG (1)
[x] @holodisc (1)
[ ] @substack (1)
[x] @vith (1)
[x] @arithmetric (1)
[ ] @xizhao (1)
[ ] @obo20 (1)
[x] @michaelsbradleyjr (1)
[ ] @mikeal (1)
[x] @mitar (1)
[x] @demmojo (1)
[ ] @nunofmn (1)
[ ] @nGoline (1)
[x] @OR13 (1)
[x] @PedroMiguelSS (1)
[x] @petethomas (1)
[x] @requilence (1)
[ ] @seungwon-kang (1)
[ ] @taravancil (1)
[x] @terichadbourne (1)
[ ] @zhiyuan-lin (1)
[x] @elsehow (1)
[x] @ethers (1)
[ ] @kumavis (1)
[ ] @leekt216 (1)
[ ] @jfmherokiller (1)
[x] @phillmac (1)
[ ] @priecint (1)
[ ] @shunkino (1)

RichardLitt commented 4 years ago

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

alanshaw commented 4 years ago

js-ipfs-http-client is being re-licensed to MIT+Apache2 and we need your sign off. Please read the info and either check the box next to your github handle, or comment on this issue thread with the following text:

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

Mentioning these people here who did not get a notification in the original list due to github limiting mentions to <= 50:

@holodisc, @substack, @vith, @arithmetric, @xizhao, @obo20, @michaelsbradleyjr, @mikeal, @mitar, @demmojo, @nunofmn, @nGoline, @OR13, @PedroMiguelSS, @petethomas, @requilence, @seungwon-kang, @taravancil, @terichadbourne, @zhiyuan-lin, @elsehow, @ethers, @kumavis, @leekt216, @jfmherokiller, @phillmac, @priecint, @shunkino

fsdiogo commented 4 years ago

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

PedroMiguelSS commented 4 years ago

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

Fil commented 4 years ago

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

filips123 commented 4 years ago

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

vmx commented 4 years ago

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

fbaiodias commented 4 years ago

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

holodisc commented 4 years ago

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

MichaelMure commented 4 years ago

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

demmojo commented 4 years ago

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

atfornes commented 4 years ago

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

vith commented 4 years ago

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

requilence commented 4 years ago

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

achingbrain commented 4 years ago

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

elsehow commented 4 years ago

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

pgte commented 4 years ago

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

maxlath commented 4 years ago

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

phillmac commented 4 years ago

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

petethomas commented 4 years ago

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

JGAntunes commented 4 years ago

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

whyrusleeping commented 4 years ago

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

OR13 commented 4 years ago

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

wraithgar commented 4 years ago

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

KrishnaPG commented 4 years ago

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

hackergrrl commented 4 years ago

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

Also: if you plan to do this to more repos, it'd be nicer to have a single sign-off list than subscribe folx to all of these threads /w single sign-offs.

mitar commented 4 years ago

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

vasco-santos commented 4 years ago

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

daviddias commented 4 years ago

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

ethers commented 4 years ago

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

arithmetric commented 4 years ago

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

terichadbourne commented 4 years ago

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

dignifiedquire commented 4 years ago

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

travisperson commented 4 years ago

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

michaelsbradleyjr commented 4 years ago

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

dostu commented 4 years ago

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

dannyid commented 4 years ago

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

ipfs-inactive / js-ipfs-http-client

Re-license js-ipfs-http-client to MIT + Apache 2 #1189

What we need to do:

Contributor sign-off: