I'm using an open source library under GPL in a closed source project. If the libraries license changes from GPL to LGPL, does it mean the previous code (written when the library was GPL) should be made open source?
3
-
4Presumably the previous code written under GPL already is open source? I don't understand this question; can you add more details?– apsillers ♦Jun 23, 2015 at 18:44
-
@what if I'm using an open source library under GPL in a closed source project and the libraries license changes from GPL to LGPL– Abdullah SaleemJun 23, 2015 at 18:53
-
7"what if I'm using an open source library under GPL in a closed source project" -- you cannot distribute GPL code in a project that is not GPL-licensed, so if you're distributing it, you were violating the GPL and may have stopped violating the GPL by switching to the LGPL. If you're not distributing it, absolutely nothing changes, because the GPL family of licenses only impact distribution.– apsillers ♦Jun 23, 2015 at 18:56
Add a comment
|
1 Answer
The GPL is already an open source license.
But if you relicense a project (and a license change from GPL to LGPL needs the permission of all contributors, I assume that this is given) does not change the license on the old code. So the previous code is still available under the GPL, nothing changes in that regard.
