-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Nelson is CLA-ware, without any disclaimer or waiver. #2326
Comments
While there indeed is a CLA, it doesn't seem to be needed to contribute, see https://github.com/Nelson-numerical-software/nelson/blob/master/CONTRIBUTING.md. Also you're not requested to agree with in on Weblate. Maybe @Nelson-numerical-software could clarify this. |
Hi, Nelson is a long term project. I (as main developper) need to have the possibility to re-licensing easily (GPL3 or LGPL3) without to ask to others contributors. Do not hesitate to contact me directly if you need more informations. Thanks for your interest about Nelson |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Nelson-numerical-software Long running projects like the Linux kernel seem to do just fine without. https://news.slashdot.org/story/14/01/20/2158221/linus-torvalds-any-cla-is-fundamentally-broken The good news is you can in fact license it GPLv3 all you like, without any CLA. If you just additionally want to make it LGPL, you can dual license it GPLv* and LGPL, though you need to trust the legality and the coverage of the CLA, and prepare for the inevitable backlash. You can then do away with the CLA. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
https://cla-assistant.io/Nelson-numerical-software/nelson.
Also, this has no legal bearing if signed on Norwegian territory.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: