Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vmx
Copy link
Member

@vmx vmx commented Feb 21, 2020

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.

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.
@vmx
Copy link
Member Author

vmx commented Feb 25, 2020

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.

@dvc94ch
Copy link
Collaborator

dvc94ch commented Feb 25, 2020

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.

@Gozala
Copy link
Contributor

Gozala commented Feb 25, 2020

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
@dignifiedquire
Copy link
Member

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

@hobofan
Copy link
Contributor

hobofan commented Feb 26, 2020

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

@bantonsson
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.

@gnunicorn
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.

@tomusdrw
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.

@tomaka
Copy link
Member

tomaka commented Feb 26, 2020

Same

@maciejhirsz
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
@vmx
Copy link
Member Author

vmx commented Feb 27, 2020

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
Member Author

vmx commented Mar 5, 2020

@koushiro as you contributed quite a lot recently, could you also please comment that you re-license your contributions?

@koushiro
Copy link
Contributor

koushiro commented Mar 5, 2020

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

@rklaehn
Copy link
Contributor

rklaehn commented Dec 11, 2020

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

Gozala commented Dec 17, 2020

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

Copy link

@Leena8686 Leena8686 left a 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

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

Successfully merging this pull request may close these issues.