There are no "real" loopholes in GPL. Let me run through an example.
If I as a developer work on some code and release it via GPL, and you
like what I have done, then you can use it however you want. If
you use it "Internally" to you organization, you don't have to do
anything special. If you decide to incorporate my GPL-ed code in
something you distribute, then the source (both mine and yours) must be
included in the distribution.
If you don't like the openness that the GPL requires you can either not
use my code, not distribute it, or find code that uses some other
license like BSD.
I know that there are some nuances around LGPL but that is the gist of GPL.
No loopholes here. GPL is about choice.
- Re: [Hardhats-members] GPL loophole article Jim Drash
- Re: [Hardhats-members] GPL loophole article Kevin Toppenberg
- Re: [Hardhats-members] GPL loophole article Todd Berman
- Re: [Hardhats-members] GPL loophole article K.S. Bhaskar
- Re: [Hardhats-members] GPL loophole article Todd Berman
- Re: [Hardhats-members] GPL loophole articl... Kevin Toppenberg
- Re: [Hardhats-members] GPL loophole ar... Michael D. Weisner
- [Hardhats-members] What is actually to... Todd Berman
- Re: [Hardhats-members] What is ac... Gregory Woodhouse
