-
Notifications
You must be signed in to change notification settings - Fork 237
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
MIT license #464
Comments
I am very interested in this, since our project cannot use this package with the current license. |
Me too. I am also very interested in using this in a large company in Germany. But I can't, and I wasted time testing this. I think the AI misled me with this package. |
The MulanPSL-2.0 we use is also a standard SPDX license. You can find it at https://spdx.org/licenses/MulanPSL-2.0.html. It's close to or even looser than the MIT license. Here's a brief difference for reference: |
The main issue with MulanPSL-2.0 is this:
It effectively means that the English version is all but irrelevant, because by definition the Chinese version could have wording that means something unexpected. So any user of software licensed under MulanPSL-2.0 should source a translation that suits their needs. |
Thank you for raising this issue. Please allow me to explain. (I'm the one responsible for drafting MulanPSL-2.0 and getting it approved by OSI.) Actually at the beginning we just say in the license, english and chinese version have the same legal effect (because we carefully translated the two versions word by word, sentence by sentence). However, the OSI community suggested that IN CASE, in case there is a conflict between the two languages, we should indicate which language prevails. However, I must say, there is a tiny chance (close to zero) that this circumstance will happen. |
Need to confirm if the license can be converted into MIT license?
If it’s MIT then we can have more usage , and suggest any guidance on this and don’t want to convert to webpack if this is not the case ?
The text was updated successfully, but these errors were encountered: