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
Comments
Do you have some guidance on how we can help with this issue as #705 is coming close to being finished haha |
I've started a spreadsheet that looks at the licenses here: https://docs.google.com/spreadsheets/d/1x1T_DRv3cyGEhlGyFtVm82MgPhNcUQz96RizURV79O8/edit#gid=0 |
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. |
First attempted license update to see if I'm doing this right: https://github.com/streetsidesoftware/cspell-dicts/pull/2624/files |
Started a draft PR here to work on more of the updates: #2627 |
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. |
I'm fine with LGPL3. |
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:
The text was updated successfully, but these errors were encountered: