Can the author of software make it proprietary after making it gpl?
-
4Anyone who has a version of the software with GPL license, AND the source code, can forever distribute that version of the software, or distribute modified versions, as long as they follow the GPL license. You can use a different license for all later versions, but it doesn't affect anyone who has an older version. – gnasher729 Jun 16 '19 at 14:23
-
Possible duplicate of Is it possible to close an open source project? – zale Jun 16 '19 at 15:51
-
3Possible duplicate of How can a project be relicensed? – Bart van Ingen Schenau Jun 16 '19 at 17:12
-
1Closely related: Is it possible for Linux developers to retroactively "pull their code" from Linux? – apsillers♦ Jun 16 '19 at 18:37
-
See also: opensource.stackexchange.com/a/8465/8868 – rage Jul 20 '19 at 14:57
Yes, the author (or whoever holds the copyright) can do as they please, changing the license at will. But only close up later versions, what was distributed under an open source license stays forever open.
Case in point is SSH: It was open source up to version 1, version 2 (clearly a development on version 1) is closed. OpenSSH took version 1 (still open source) and created an extension handling the new protocol, released as open source.
-
1"what was distributed under an open source license stays forever open" I'm not sure that's entirely true. It's perfectly possible for me to take code to which I own the rights, and which I was distributing under (say) GPLv3, and instead start distributing it under a proprietary licence. People who have already got it from me are completely entitled to continue to use it under the terms of GPLv3, and distributing it themselves (under GPLv3) should they wish to. But I am not obliged to continue doing so should I choose not to. However, that's a fine point, and mostly I agree with you. – MadHatter♦ Jul 18 '19 at 9:00
-
@MadHatter, a license gives the recipient certain rights (in the open source license cases, it includes the perpetual right yo modify and distribute). The author can't just take that away. – vonbrand Aug 4 '19 at 14:58
-
The author (well, rightsholder) can't take that away from people to whom (s)he has already given it, I agree - but (s)he is completely free to stop giving those rights to future recipients of the code. – MadHatter♦ Aug 4 '19 at 15:06
-
@MadHatter, if someone got the right to redistribute, they can still do so. If I decide not to distribute directly anymore makes no difference. – vonbrand Aug 4 '19 at 15:09
-
I completely agree there's no practical difference, assuming you (wanting a copy of the code under the original licence) can find an earlier recipient thereof, and they agree to give you a copy. It's a fine point I'm making, as I think I've said already - but to say the rightsholder can "only close up later versions" is, at least, ambiguous. Some people think that once you've distributed
foo-1.1.1aunder GPL you are obliged always to do so, and that's simply not so. – MadHatter♦ Aug 4 '19 at 15:16
