3 ms·
tldr; if you fork gpl code, you have to gpl your fork. People love to hear themselves talk, myself included.
by jimmyvalmer 5y ago
tldr; if you fork gpl code, you have to gpl your fork.
People love to hear themselves talk, myself included.
- pacifika 5y agoI don’t think that’s quite correct. you need to publish the software before this kicks in. If you fork a web framework and build a website with it for example you don’t have to GPL the website. If you sell or make the fork available then it does, is my understanding.
- jimmyvalmer 5y agoA tree falling in the forest can either make a sound or not. If someone is looking however, it must emit a sound. In that sense your criticism is a vacuous one.
- CorrectHorseBat 5y agoThe website would be GPL, but since you're not giving anyone binaries you also don't have to give anyone the source.
- rhplus 5y agoDistribute is the key word. In general, companies can fork GPL code to power the backend of public or internal services, without being required to publish their modifications, but once they distribute the software (allowing binaries/scripts to be downloaded, including it in app, embedding it in firmware...), then they must open up the source.
- stavros 5y agoYou do if the license is AGPL 3.