3 ms·
For everyone bringing up the GPL licence, strait from the horse's mouth: > The GPL does not require you to release your modified version. You are free to make
by Mikeb85 13y ago
For everyone bringing up the GPL licence, strait from the horse's mouth:
> The GPL does not require you to release your modified version. 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.
http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLRequireSourcePostedPublic http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GP...
Distributing the code within a company/organization does NOT constitute 'distribution', and does NOT require you to release your code.
Edit - and in the licence itself - Version 3 of the GPL
> “The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
And
> To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
http://www.gnu.org/copyleft/gpl.html http://www.gnu.org/copyleft/gpl.html
- revelation 13y agoOrganization seems like an odd qualifier. Certainly you have to make the code available to everyone you delivered modified binaries to, and at GPL conditions (meaning they are then free to further distribute it, per GPL)?
- Mikeb85 13y agoNot according to the GSF's website. Besides, let's face it, GS employees likely don't have any 'secret' code anywhere near their computers. It likely lives on their mainframes, and only there.
- revelation 13y agoWell, it's an FAQ, it's a simplification, not the actual legally binding license. I can't find any mention of "organization", but I do find these parts (GPLv2): 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: [give access to the sourcecode] Meaning everyone you distribute a copy to, you have to give access to the sourcecode, too, or provide instructions on how to get the sourcecode. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. Meaning distributing the program to someone gives them the full rights under the GPL. (IANAL, so I'd be very pleased to be corrected here. Maybe the FAQ made the assumption that corporations have other means to keep employees from exercising GPL rights? Or maybe the license is to the corporation as a whole, and it itself can't break the GPL unless it distributes it to different entities?)
- Mikeb85 13y agoFrom section 0 of the GPL v3 > “The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations. And > To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. http://www.gnu.org/copyleft/gpl.html http://www.gnu.org/copyleft/gpl.html
- lambda 13y agoYes, I believe that the license is for the corporation as a whole, so it using it internally does not count as distribution.
- SourPatch 13y agoI don't know why everyone keeps bringing this up. The whole point of the license applies to distribution. Even if it said you should distribute privately used modifications, that is unenforceable and stupid.