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

The license instructions are confusing in EULA vs the repository's README - need clarification #1078

Closed
Sd100 opened this issue Feb 19, 2021 · 1 comment · Fixed by #1080
Closed

Comments

@Sd100
Copy link

Sd100 commented Feb 19, 2021

Goal:
Trying to see if using data grid from material-ui-x for production is legally allowed or not.

Groundwork:
In store, it shows the license as EULA:
https://material-ui.com/store/items/material-ui-x/
https://docs.google.com/document/d/1nkd5JP5wCefo6UwpVi6PnbTaw8DxhstkCZlfHV5ZgfI/edit?usp=sharing

But in readme of this repo, it shows datagrid - MIT license and x-grid - Commercial license,

Query:
so when i import material-ui-x - does it mean i am allowed to use Data-grid in production environment of my project (saleable to customers)
OR
are they available freely for development and learning purposes only.
Can someone help clarify/confirm urgently?

Raised as issue, since new users to license agreement's complex terms the readme kind of is throwing me in doubt. So after above answer, can somone also update the readme or else once i get an answer i can try to raise a PR to update the same for clarity to developers/consmers.

Thanks in advance.

@Sd100 Sd100 added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Feb 19, 2021
@oliviertassinari
Copy link
Member

See the license in the npm package you are importing:

@oliviertassinari oliviertassinari removed the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants