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

Review Licenses for each of the dictionaries #441

Open
Jason3S opened this issue May 30, 2021 · 7 comments
Open

Review Licenses for each of the dictionaries #441

Jason3S opened this issue May 30, 2021 · 7 comments

Comments

@Jason3S
Copy link
Collaborator

Jason3S commented May 30, 2021

The Licenses need to be reviewed for each of the dictionaries that are built from 3rd party sources.

Related to #440

Links:

A few notes:

From Top 10 Questions About the Apache License | Mend:

Is the Apache license copyleft?
No. The Apache 2.0 License is permissive. It allows you to use, modify, and distribute the licensed software, including creating derivative works, without requiring those derivative works to be licensed under the same terms. You can release the modified parts of the code under any license you prefer.

There are some obligations. You must release all the unmodified parts of the software under the same license (the Apache License), and you must include copyright and attribution notices, disclaiming warranties, and provide a copy of the license with any distribution of the software.

@Ki-er
Copy link
Collaborator

Ki-er commented Jul 30, 2023

Do you have some guidance on how we can help with this issue as #705 is coming close to being finished haha

@calvinballing
Copy link
Collaborator

I've started a spreadsheet that looks at the licenses here: https://docs.google.com/spreadsheets/d/1x1T_DRv3cyGEhlGyFtVm82MgPhNcUQz96RizURV79O8/edit#gid=0

@Jason3S
Copy link
Collaborator Author

Jason3S commented Oct 7, 2023

@calvinballing,

Wow, that is impressive. You put a lot of work into that.

Thank you.

I believe GPL and LGPL are very close to each other. My understanding is that GPL is slightly stricter than LGPL (since LGPL is intended to be linked as a library).

I have been trying to have the dictionary license match the source license if there is one.

I'm not sure about CC0, I have not fully looked into it.

@calvinballing
Copy link
Collaborator

First attempted license update to see if I'm doing this right: https://github.com/streetsidesoftware/cspell-dicts/pull/2624/files

@calvinballing
Copy link
Collaborator

Started a draft PR here to work on more of the updates: #2627

@Maxim-Mazurok
Copy link
Contributor

Hi guys, I'd like to use Spanish dict but it's under GPL3 currently so corporate policy won't let me install it. I checked that source doesn't have license, and hunspell license seems to allow a choice of GPL3, LGPL3 and MPL.
If we could list all 3 of them in package.json - that would help, or just choose LGPL3 which seems to allow usage in proprietary software without the need to make it open-source.
Thank you!

@Jason3S
Copy link
Collaborator Author

Jason3S commented Apr 3, 2024

Hi guys, I'd like to use Spanish dict but it's under GPL3 currently so corporate policy won't let me install it. I checked that source doesn't have license, and hunspell license seems to allow a choice of GPL3, LGPL3 and MPL. If we could list all 3 of them in package.json - that would help, or just choose LGPL3 which seems to allow usage in proprietary software without the need to make it open-source. Thank you!

I'm fine with LGPL3.

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

No branches or pull requests

4 participants