2 ms·
The GPL's terms do not allow someone to make a derivative and then 'distribute' it to some (such as paying clients), unless they also make the source available
by gojomo 16y ago
The GPL's terms do not allow someone to make a derivative and then 'distribute' it to some (such as paying clients), unless they also make the source available to others under the GPL.
But, if an unethical or confused competitor did convert your GPL'd code into a proprietary release, you'd still need to find out, raise a public objection, and possibly threaten/file a lawsuit to truly 'enforce' the terms.
- metonymie 16y agoI understand but "make the source available to others under the GPL" may mean give their clients source code under the GPL, not necessarily publishing said source code on the internet. (Though of course, the client may publish it on their own). Or I'm missing something and they do have an obligation to make it accessible? Anyhow I have chosen the Apache License. Thank you for clearing my doubts and for your reply.
- gojomo 16y agoYou should ask the FSF (the foundation around the GPL) for the finer details of their preferred interpretation. By my reading, essentially, anyone who gets a copy of the modified work must also be given the right to give it to others, and to get the source code. I suppose your competitor could try to conspire with some small, cohesive group of customers to hide from you any evidence/copies of their derivative product. But, the competitor can't make this secrecy a license condition of using what they built from your code, without also violating the GPL's terms. So you could then go after them for violating your copyright, if you know they've added license terms. (If they have violated your copyright/license, the remedy isn't automatically that you or anyone else gets their source code under the GPL; it could be some other correction/settlement/damages.)
- metonymie 16y agoI have contacted the FSF on one occasion ( regarding a patent problem ) and they weren't very responsive. I have already decided on the Apache license 2 for this version of the project. But it's just a quick and dirty release that is intended to showcase the technology. I might in the future have to port it to a another language ( the project is too dependent on a library that's not actively being maintained and I might have to write my own version ). If I do this I will definitely look at the GPL license. Again, Thank you for the reply.