-
Notifications
You must be signed in to change notification settings - Fork 110
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
GPL3.0 #19
Comments
If you'd look at issue #13, copyleft seems to be a deliberate choice, yes. |
Yes, GPL3 is a very hard license, it means that you need to share not only your library when used, but also any code that you compile together with your library. I'd recommend something lighter light the MIT license, (i.e. https://github.com/SpinalHDL/VexRiscv/blob/master/LICENSE ) , Apache license, or similar. But anyway, I would like to use the lines here to congratulate you for the impressive work you have done here @WangXuan95 Thank you for sharing with us all!. |
Also look at LGPL, this would help wider adoption of your library, while still ensuring that people will contribute back fixes and code to FPGA-USB-Device. |
Please consider Apache2/MIT, it might be a showstopper for us to use together with our research oriented open source RISC-V. |
I also hope the license will be changed to Apache2/MIT. I believe people want to use this great project easily, not with GPL3.0. |
@perlindgren @jokinen086 @the-moog @mangelajo I've change the license to LGPL |
Thank you @WangXuan95 your code will reach to many projects. And I hope that you will get good contributions back 👏👏 |
Thank you @WangXuan95 for changing the license. |
Is this source code deiberately GPL3.0?
Only that means that, as it stands, this project can only be used in GPL3.0 compatible 'copy left' hardware as the act of synthisising it and loading into an FPGA is akin to a static link.
Giving both project owners and contributors equal access and rights to both sets of IP. That makes using this in any commercial product almost impossible, even if not for profit, e.g. internal test equipment.
Would you consider adopting a similar but less restrictive license, e.g. Apache or MIT? Or perhaps dual licence?
The text was updated successfully, but these errors were encountered: