Contents
Which is not a distribution under the GPL license?
You are complying with everything in the license. Anyone who can get a distribution needs the source. Services over the network is not considered distribution. If a GPL project produces awesomeProduct.jar, any place that awesomeProduct.jar exists, awesomeProduct_src.jar also needs to exist.
What are the options for compliance with the GPL?
GPL’s binary distribution sections offer a choice of compliance methods, each of which we consider in turn. Each option refers to the “Corresponding Source” code for the binary distribution, which includes the source code from which the binary was produced.
Is it legal to use GPL code in a proprietary, closed?
An “original work” that uses code from another source is in fact a derivative work of both the original work and the other source, and it is the derivative work that is required to be licensed under the GPL. The original work remains under whatever licence it had before.
Is the GPL code in a derivative work public?
Now, the entirety of the original work has been copied into a work that is GPL licenced and thus the source code is public, so the original work’s code is now public, true. But it is public because it was included in a derivative work. It’s a subtle but important difference.
What does GPL mean for open source software?
The result is that any software that uses any GPL open source component (regardless of its percentage in the entire code) is required to release its full source code and all of the rights to modify and distribute the entire code. 2. What are the GPL license terms and conditions?
What do you need to know about the GPL?
If you commercially distribute binaries not accompanied with source code, the GPL says you must provide a written offer to distribute the source code later. When users non-commercially redistribute the binaries they received from you, they must pass along a copy of this written offer.
What’s the difference between GPL2 and GPL3?
But all the discussion I have seen over GPL2/GPL3 distribution has been about webservices – not about internal use. The essence of the GPL is that it does not limit what you can do with the software — it imposes requirements on you when you Convey or Propagate the covered work.