2 ms·
At least, you keep the source code in the open, and the changes stay in the open. It's giving enough, when compared to BSD/MIT and similar "permissive" licenses
by bayindirh 4y ago
At least, you keep the source code in the open, and the changes stay in the open. It's giving enough, when compared to BSD/MIT and similar "permissive" licenses to fork away without making anything available.
- pabs3 4y agoNo, the changes don't have to stay in the open, they only have to get given to your downstream users, not publicly in the open and not back to the upstream project. You can definitely fork a GPL project without making anything public, although your users can choose to make the modified code that you send to them public, but they might not ask for it or might not publish it if they do get it.