3 ms·
Does this link satisfy you? https://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html https://www.softwarefreedom.org/resources/2007/gpl-no
by foobarbazqux 13y ago
Does this link satisfy you?
https://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html https://www.softwarefreedom.org/resources/2007/gpl-non-gpl-c...
I'm sure that one could contrive a GPL wrapper project to contain the BSD kernel. Nobody ever said anything about removing copyright notices or breaking license terms.
- jmillikin 13y ago> Nobody ever said anything about removing copyright > notices or breaking license terms. You did. Your earlier posts stated: > almost all non-GPL open source code can be relicensed as GPL. and > changing a license to GPL does not violate the conditions of the BSD Which, to me, appear to be clear and unambiguous statements that you feel it's legal to take some BSD-licensed code and change its license to the GPL.
- foobarbazqux 13y agoI agree that I could have been more precise. Again, I thought this was widely understood. I apologize for my lack of clarity. I was never suggesting some extra-legal method; it simply didn't occur to me because I would never consider this in a software licensing discussion. When I say relicense a BSD project under the GPL, I mean take the existing codebase and go through whatever legal steps are necessary (without additional permission from the copyright owners) such that the resulting distribution can accept future contributions under the GPL. So do you now understand what I mean, and see that it's possible with the right legal wrangling, per the link from the Software Freedom Law Center?