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

I'm worried that prohibiting usage on those ccTLDs is against MIT #2573

Closed
KisaragiEffective opened this issue Dec 9, 2022 · 2 comments
Closed

Comments

@KisaragiEffective
Copy link

MIT license said:

The MIT License (MIT)

Copyright (c) 2014 Tristan Edwards & Limon Monte

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Bold: by @KisaragiEffective

I'm worried about this change. It can be read like "I, @limnote, does prohibite use in any form on those ccTLDs."

However, the MIT license promised no limitation for use.

What do you (especially @limonte, @zenflow, and @toverux) think about this? Most of end-users does not notice about this change.

IMHO:

  • revert this change
  • or, you change LICENSE and package.json to reflect about it.
@limonte
Copy link
Member

limonte commented Dec 9, 2022

Thank you @KisaragiEffective you raised a good question.

The prohibition might be indeed incompatible with MIT. Instead of prohibiting usage on .ru, .su, .рф ccTLDs, I now clearly describe the different behavior for them: 8dc7174

So, russians are still free to use the plugin and it'll act according to the README 🤗

That should be compatible with MIT:

THE SOFTWARE IS PROVIDED "AS IS"

WDYT?

@limonte limonte closed this as completed Dec 9, 2022
@limonte limonte reopened this Dec 9, 2022
@KisaragiEffective
Copy link
Author

KisaragiEffective commented Dec 9, 2022

WDYT?

Sure, I think it has solved this. Thank you for quick review 🚀

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

No branches or pull requests

2 participants