Skip to content
This repository has been archived by the owner on Mar 10, 2020. It is now read-only.

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

Open
40 of 77 tasks
alanshaw opened this issue Nov 29, 2019 · 37 comments
Open
40 of 77 tasks

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

alanshaw opened this issue Nov 29, 2019 · 37 comments

Comments

@alanshaw
Copy link
Contributor

alanshaw commented Nov 29, 2019

@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 #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:

@RichardLitt
Copy link
Contributor

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

@alanshaw
Copy link
Contributor Author

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
Copy link
Contributor

fsdiogo commented Nov 29, 2019

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

22 similar comments
@PedroMiguelSS
Copy link
Contributor

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

@Fil
Copy link
Contributor

Fil commented Nov 29, 2019

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

@filips123
Copy link
Contributor

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

@vmx
Copy link
Contributor

vmx commented Nov 29, 2019

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

@fbaiodias
Copy link
Contributor

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

@holodisc
Copy link
Contributor

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

@MichaelMure
Copy link
Contributor

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

@demmojo
Copy link
Contributor

demmojo commented Nov 29, 2019

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

@atfornes
Copy link
Contributor

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

@vith
Copy link
Contributor

vith commented Nov 29, 2019

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

@requilence
Copy link
Contributor

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

@achingbrain
Copy link
Collaborator

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

@elsehow
Copy link
Contributor

elsehow commented Nov 29, 2019

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

@pgte
Copy link
Contributor

pgte commented Nov 29, 2019

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

@maxlath
Copy link
Contributor

maxlath commented Nov 29, 2019

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

@phillmac
Copy link
Contributor

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

@petethomas
Copy link
Contributor

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

@JGAntunes
Copy link
Contributor

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

@whyrusleeping
Copy link
Contributor

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

@OR13
Copy link
Contributor

OR13 commented Nov 29, 2019

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

@wraithgar
Copy link
Contributor

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

@KrishnaPG
Copy link
Contributor

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

@hackergrrl
Copy link
Contributor

hackergrrl commented Nov 30, 2019

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
Copy link
Contributor

mitar commented Nov 30, 2019

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

3 similar comments
@vasco-santos
Copy link
Contributor

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

@daviddias
Copy link
Contributor

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

@ethers
Copy link
Contributor

ethers commented Nov 30, 2019

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

@arithmetric
Copy link
Contributor

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

@terichadbourne
Copy link
Contributor

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

1 similar comment
@dignifiedquire
Copy link
Contributor

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

@travisperson
Copy link
Contributor

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

3 similar comments
@michaelsbradleyjr
Copy link
Contributor

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

@dostu
Copy link
Contributor

dostu commented Dec 5, 2019

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

@dannyid
Copy link
Contributor

dannyid commented Jan 12, 2020

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests