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

licensing issues #108

Open
esaule opened this issue Apr 3, 2020 · 2 comments
Open

licensing issues #108

esaule opened this issue Apr 3, 2020 · 2 comments
Assignees

Comments

@esaule
Copy link
Member

esaule commented Apr 3, 2020

All, (in particular @krs-world , @j2payton , @esaule )
The question of which software license we should apply to the bridges clients arose because of a wave file parsing library we wanted to use which is released under gpl v3.
I am personally a fan of GPL v3. But that license would mean that all student assignment would automatically have to be GPLv3 as well. So I feel that may be too much. I feel like the better one would be LGPL v3.
The question is opened to everyone, so let's discuss this.

@esaule
Copy link
Member Author

esaule commented Apr 12, 2020

I did not see any response to that. Should we we go for LGPL? (assigning a few people to make sure you see it)

@AlecGoncharow
Copy link
Contributor

So if I understand this correctly, if we chose LGPLv3 that would shield student code from also being GPLv3? If that's the case then I see no drawbacks. Event still it seems GPLv3 is still a quite permissive license as far as private use goes. As it is unlikely we will run into the issue of trying to distribute compiled binaries of bridges driver code that is also closed source.

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

4 participants