An important point some people miss about GPL is that it's perfectly valid to use GPL-ed code for in-house software. Suppose you write a tool just for internal use, and this tool is never released. You are free to use libraries and other code licensed with GPL in this tool, without releasing anything. If, in the future, you'll want to release the tool online and/or sell it, you'll have to license it with GPL as well. Here's the relevant quote from the GPL FAQ:
Does the GPL require that source code of modified versions be posted to the public? The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization. But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL. Thus, the GPL gives permission to release the modified program in certain ways, and not in other ways; but the decision of whether to release it is up to you.


comments powered by Disqus