2 ms·
I put code under a BSD license, so on many occasions I've been prevented from using GPLed code. BSD and GPL are not incompatible. BSD and GPL pieces can be com
by kazinator 4y ago
I put code under a BSD license, so on many occasions I've been prevented from using GPLed code. BSD and GPL are not incompatible. BSD and GPL pieces can be combined into a single program, while retaining their individual licenses; the problem is that the combination has to be redistributed under the GPL. Compatibility is not the only question, but what kind of compatibility: what must the master license be if the combination is made.
Cygwin changing to the LGPL back in 2016 enabled me to distribute BSD code with Cygwin DLL's without having to GPL the code. When I learned from the Cygwin mailing list about this change, I immediately set to work to create a fork of the Cygwin DLL which provides more native-like behaviors, to be used as run-time library for programs. Had they not announced a licensing change, I'd not have done anything of the sort.
- torstenvl 4y agoHave you considered releasing your code under both BSD and GPL?
- kazinator 4y agoNo; it makes no (logical) sense.
- torstenvl 4y agoIt obviously does. You wish to use a permissive license; the GPL requires that you provide distributes your code under the GPL; dual-licensing meets both of these requirements. Care to explain the thinking behind you reaching the opposite conclusion?
- kazinator 4y agoIf I offer you a program under the BSD license, and then offer you exactly the same program under the GPL licnese, I have effectively offered you the program under the BSD license. Everything you could want to do with the program is granted by the BSD license maximally; the GPL doesn't grant you anything new. And the BSD offer nullifies all restrictions imposed by the GPL. There is no benefit in such a dual licensing idea, and so if there is any nonzero harm, there is a net harm. What are you going to do if a contributor sends you a significant patch that you would like? Only, oops, their contributions are under the GPL because they are working with your GPL offering? Suppose that person believes in the GPL and won't switch to the BSD. If you accept that, you will have to fork the program into two. If you make it clear that all contributions must be dual-licensed, then there isn't really any meaning. Those who favor the GPL aren't going to contribute to a project that requires them to BSD-license their contribution alongside the GPL, because it negates the GPL. If you don't agree with the redistribution terms of the GPL, then just don't use it. BSD, MIT or whatever. It's clear to all potential contributors that they must use the same license in order to get their changes merged, and that's it; no ambiguity, no confusions leading to forking.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]