-
Notifications
You must be signed in to change notification settings - Fork 52
feat: change license from MIT to MIT + Apache 2.0 (from 2020 onwards) #177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
In order to unify the licenses across several multiformats repositories I propose changing the license to an MIT + Apache 2.0 dual license. In order to make this change, it needs to be approved by all contributors. If you agree with such a license change, please respond to this PR with: > I license past and future contributions under the dual MIT/Apache-2.0 license, > allowing licensees to choose either at their option.
I hereby ping all the current contributors since April 2020 (@Arqu @woss @edouardparis @galargh @hanabi1224 @Kubuxu @kayabaNerve @mattheworris @mxinden @paolobarbolini @Stebalien @thomaseizinger @tyshko5 @vmx) to please agree to the license change with replying to this PR with:
|
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, |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
2 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, |
I license past and future contributions under the dual MIT/Apache-2.0 license, |
I license past and future contributions under the dual MIT/Apache-2.0 license, |
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 contributions to multiformats/rust-cid predating July 1st, 2025 under the dual MIT/Apache-2.0 license, I'm unsure what contributions I've made in the past but that should be sufficient. If it isn't, please let me know and I'll do my best to issue the necessary statement (as I unfortunately can't reasonably use the requested format). Thank you for asking permission from contributors and doing this properly. |
I license past and future contributions under the dual MIT/Apache-2.0 license, |
In order to unify the licenses across several multiformats repositories I propose changing the license to an MIT + Apache 2.0 dual license.
In order to make this change, it needs to be approved by all contributors.
If you agree with such a license change, please respond to this PR with:
This is a follow up from #25. I created a new PR as I didn't want to create notify spam to the ones that already agreed.
This also leads to some notification spam, I'm sorry for that, but I think that's the best/easiest/most transparent way of doing it.