You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: