-
Notifications
You must be signed in to change notification settings - Fork 299
Re-license js-ipfs-http-client to MIT + Apache 2 #1189
Comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
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:
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 |
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
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
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. |
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
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
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
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
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
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
@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:
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:
Contributor sign-off:
The text was updated successfully, but these errors were encountered: