Closed alanshaw closed 1 year ago
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.
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.
js-ipfs is being deprecated in favor of Helia. You can learn more about this deprecation and read the migration guide.
Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterwards (see https://github.com/ipfs/js-ipfs/issues/4336).
@achingbrain @BigLep you two might want to peek at this
@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 https://github.com/ipfs/js-ipfs/pull/2620, 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: