-
Notifications
You must be signed in to change notification settings - Fork 51
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
feat: change license from MIT to MIT + Apache 2.0 #25
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 (@dignifiedquire @maciejhirsz, @tomusdrw, @tomaka, @leavehouse, @hobofan, @dvc94ch, @gnunicorn, @rklaehn @bantonsson @Gozala) 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. Still not sure what the point is, other than license supremacy and exterminating the lesser licensing options. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
5 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. |
Same |
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. |
@koushiro as you contributed quite a lot recently, could you also please comment that you re-license your contributions? |
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approval for change MIT to MIT M+ Apache 2.0
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: