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.

Sign up for GitHub

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

Jump to bottom

Changing the license to MIT #88

Open
robinlahtinen opened this issue Mar 6, 2023 · 1 comment
Open

Changing the license to MIT #88

robinlahtinen opened this issue Mar 6, 2023 · 1 comment
Assignees
@robinlahtinen
Milestone
v1

Comments

@robinlahtinen
Copy link
Member

robinlahtinen commented Mar 6, 2023 •
edited
Loading

I'm thinking of changing the license to MIT from MPL-2.0, due to MPL probably being too restrictive for closed source projects that want to customize the Material Design Light design tokens (theme). Interested to hear opinions for or against the change!
@robinlahtinen robinlahtinen added the enhancement New feature or request label Mar 6, 2023
@robinlahtinen robinlahtinen changed the title Changingt license to MIT Changing the license to MIT Mar 6, 2023
@robinlahtinen robinlahtinen self-assigned this Mar 6, 2023
@robinlahtinen robinlahtinen removed the enhancement New feature or request label Mar 6, 2023
@robinlahtinen robinlahtinen added this to the v1 milestone Mar 6, 2023
@stephanebastian
Copy link

I don't have a strong opinion on this topic, but as I would definitely +1 a change to MIT or Apache 2.0. Not so much because one is better than the others but rather because I believe they are more popular, and better known by developers than MPL. Thus better for the adoption of your open-source project. I've used many open source libraries and most of the them were Apache 2.0 or MIT. Some of them were Eclipse public license and very few of them were MPL
FWIW: https://www.slant.co/topics/1141/~best-open-source-licenses

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@robinlahtinen robinlahtinen

Labels
None yet
Projects
None yet
Milestone
v1
Development

No branches or pull requests
2 participants
@stephanebastian @robinlahtinen