3 ms·
> You can always fork the code, put the GPL on it and distribute it under those terms if you want. They can GPL their changes, but your original copyright and
by protomyth 13y ago
> You can always fork the code, put the GPL on it and distribute it under those terms if you want.
They can GPL their changes, but your original copyright and license stands[1]. If it was any other way, the GPL would be no protection.
1) unless you go public domain or grant the ability to change the license which the BSD does not.
- wbhart 13y agoThere is a difference between the license under which a project is distributed and the license of individual contributions. Any GPL project can use BSD contributions. The overall license of the project remains GPL. The opposite is not true. A BSD licensed project cannot incorporate GPL code, otherwise the project becomes a GPL project, not a BSD one.
- protomyth 13y agoA mixed project's source files are BSD & GPL, it has to obey both. The BSD requirements[1] have to be honored as well as the GPL and any other licensed used. 1) such as "Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution."
- belorn 13y agoBy defining it as BSD project or and GPL project, one basically make two stand points. 1: The license choice is a political one. Picking the BSD license (or GPL) is equal to doing a political message. 2: The key feature of the project is defined by the circumstances that permission is granted to use, copy, and distribute.