News for hackers. Stuff that matters.
Re:The time has come to stand up for the GPL by joshyeager on Friday March 06, 2015 @11:02AM (#9157693)
The problem is that no one really knows what constitutes "safe" use of GPL code. Even in a highly-technical OSS-friendly community like HN, there are many different interpretations of what the GPL's restrictions actually mean. You can see this in action in these VMware threads, where there are strong arguments on both sides about whether VMware is violating the GPL.

That uncertainty plus the viral nature of the GPL means that there's no way to know for sure that you won't be forced to open your whole codebase at some point in the future. That's more risk than a proprietary software company is willing to take.

The only way to resolve this problem is to get legal decisions like this one. One way or the other, this decision will clarify the picture slightly. If we add enough other decisions, maybe someday we'll have clarity.

Until then, my company is solidly in the "Absolutely no GPL" camp.

Re:The time has come to stand up for the GPL by lambda on Friday March 06, 2015 @12:36PM (#9158289)
There is a pretty clearly defined set of safe behaviors under the GPL. If you do not link to a program, run it in the same address space as your proprietary code, or use any internal data structures of that program, that is safe.

No one can force you to open your whole code base. They can only make you choose between opening the parts that do the unsafe things listed above (linking, running in the same address space, utilizing private data structures via some kind of shim that is supposed to work around the GPL), or they can force you to stop distributing the GPLed software.

  Until then, my company is solidly in the "Absolutely no 
  GPL" camp.
It's so stunningly easy to use GPLed software properly, and there are thousands of companies doing it. Just don't link it to your code, or try to do some kind of hack that avoids linking it while giving you all of the same benefits of doing so.

The problem with VMware is that they have been pushing all of the boundaries; rather than just taking the easy road and doing known safe things like ensuring that there's a clear separation between GPLed code and their code, or just releasing their code that is linking to the GPLed code.

Re:The time has come to stand up for the GPL by glass- on Friday March 06, 2015 @01:33PM (#9158624)
The GPL has some fun semantics.

Take MediaWiki, it is GPL licensed (not AGPL), so you can modify it and run an instance of it without sharing your changes. Except, when someone accesses it, you are redistributing MediaWiki's GPL-licensed JavaScript files to their browser, so you do have to share your changes[0]. Think how many sites there are violating that without even realising.

Now think how you configure MediaWiki; you modify LocalSettings.php to (at the bare minimum) add the database username/password, and set the secret key.

This means essentially every site running a MediaWiki installation (or Wordpress, or effectively any other GPL-licensed web application) is violating the GPL, and are only getting away with it because no one has bothered to take legal action over it.

[0] http://lwn.net/Articles/609709/ (section: "JavaScript and the GPL")

Re:The time has come to stand up for the GPL by belorn on Friday March 06, 2015 @05:25PM (#9159993)
That is not a problem with MediaWiki, but that copyright on JavaScript has not been acknowledged or enforced since it was created. Site like archive.org, spiders, and scrapers are regularly copying JS, and most JS libraries I have seen lacks any copyright information whatsoever. Many media sites gives out JS snippets for users to include (for inline video, images and so on), but do not add a license permission to include (copy) the JS.
Re:The time has come to stand up for the GPL by tjr on Friday March 06, 2015 @01:46PM (#9158696)
I am not familiar with the inner workings of MediaWiki; how does modifying the credentials in LocalSettings.php change the JavaScript code?
Re:The time has come to stand up for the GPL by glass- on Friday March 06, 2015 @02:03PM (#9158817)
You modify LocalSettings.php which creates a derivation of MediaWiki, or as the GPL puts it, "thus forming a work based on the Program". At this point you don't have to share the changes.

However, once you distribute the JavaScript files:

"You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License [...] These requirements apply to the modified work as a whole."

By modifying LocalSettings.php you have created a derivation. By redistributing the JavaScript files you have distributed part of the work and therefore must make the whole derived work available under the GPL.

Re:The time has come to stand up for the GPL by tjr on Friday March 06, 2015 @02:13PM (#9158896)
Thank you; I misunderstood.
Re:The time has come to stand up for the GPL by joshyeager on Friday March 06, 2015 @01:02PM (#9158442)
How does that help if the code we want to use is a library? A recent example was an image manipulation need. We found a great library that met all our requirements, but was GPL. Our other options were an inferior MIT-licensed library, an inferior commercial library, or spending the time to write our own.

If the thing you want to use is a DLL, how do you use it without linking to it? Writing some sort of external process and using IPC to talk to it might fulfill the letter of the license, but it's more work and less robust, and still violates the spirit of the GPL.

In the end, we picked the MIT licensed component and worked around the issues.

Re:The time has come to stand up for the GPL by foobarqux on Friday March 06, 2015 @01:25PM (#9158575)
Your real complaint is that you can't use the GPL without the conditions imposed by it, not that those conditions are confusing or surprising.
Re:The time has come to stand up for the GPL by lambda on Saturday March 07, 2015 @11:32PM (#9164543)
You either decide not to use it, using another component with a different license or writing it yourself, or you release you code under the GPL.

That's not so hard, is it?

It's just like the question you get when using proprietary software. If you don't want to pay the license fee or abide by its terms and conditions, you find an alternative or write an alternative yourself.

The obligation to release your code is just the license fee for the GPL. If that's too steep for you, look somewhere else.

Re:The time has come to stand up for the GPL by johnny22 on Saturday March 07, 2015 @04:15AM (#9161417)
that was the right thing to do in that case.
Re:The time has come to stand up for the GPL by tomjen3 on Saturday March 07, 2015 @04:15AM (#9161416)
You can make a shim in the gpl code that connects to a socket and communicates in json and then you avoid the problem.
Re:The time has come to stand up for the GPL by derf_ on Friday March 06, 2015 @12:23PM (#9158200)
I don't think that's true at all. Anyone who's spent any time at all in open source has a pretty good idea what their obligations under the GPL are. There may be corner cases debated on the internet by geeks who ANAL, but if those actually matter to your business, simply asking someone at the SFC or SFLC will quickly clear them up [0].

I'll quote LWN's summary [1] from the talk Bob Young of Red Hat gave at LCA this January:

He has long been a staunch advocate of the GPL, he said, but not because he has detailed opinions of the differences between it and other, similar licenses. Rather, he said, he learned early on that customers do not care about the details of free-software licenses, and that diving into an explanation of them was the fastest way to send a potential customer running toward the competition. ...

With the GPL, everyone knows what the rules are, more or less, so the debate is over quickly. They might not actually know the rules, he added, but they think they do, which amounts to the same thing. As a "business guy," he said, he is always trying to simplify the "pitch" - the GPL tells everyone "what we're about," so it has the greatest impact.

[0] We did this when we wanted to publish a royalty-free patent license tied to certain code, and wanted to be sure it would not keep people from using that code in GPLv3 projects. We were reasonably sure of our interpretation of the terms, but it's always nice to double-check.

[1] https://lwn.net/Articles/629413/

Re:The time has come to stand up for the GPL by 27182818284 on Friday March 06, 2015 @11:14AM (#9157763)
>The problem is that no one really knows what constitutes "safe" use of GPL

Outside of a business that can hire lawyers, it would be helpful for the FSF and sites like http://opensource.org/licenses/BSD-3-Clause to have examples right beneath the licenses. Something like: "Here is a JS plugin with BSD-3 here is another plugin based on it. Note how the license did/didn't change." "Here is an MIT license and an example of a company adding that code to their app with license intact on the app's about screen". Stuff like that. http://choosealicense.com/ is helpful, and part of the way there.

Re:The time has come to stand up for the GPL by jordigh on Friday March 06, 2015 @12:38PM (#9158300)
> Outside of a business that can hire lawyers, it would be helpful for the FSF and sites like http://opensource.org/licenses/BSD-3-Clause to have examples right beneath the licenses

They can't do that. The law doesn't work like that. The GPL FAQ[1] has to be deliberately vague about some things, because judges and juries themselves are vague, as are the laws they work to interpret. You can't have cut-and-dry examples of what can be done and what can't, because there can be many other externalities that could make a different case work in a different way, despite similarities to your proposed list of examples.

There are can be broad strokes, but the law is not a programming language. Recent xkcd comes to mind.[2]

[1] https://www.gnu.org/licenses/gpl-faq.html

[2] http://xkcd.com/1494/

Re:The time has come to stand up for the GPL by nymisunderrated on Saturday March 07, 2015 @08:35PM (#9164044)
The organizations with lawyers behind them won't, and quite can't, do it. They're not supposed to give legal advice in general terms, no one is.

Now, if individuals would be willing to work together to put up such a site, as a collection of information and opinions, with necessary disclaimers so that its limits are well-understood, and add examples, thoughts about them, critique and disagreements about them too, that would be different.

Re:The time has come to stand up for the GPL by jordigh on Friday March 06, 2015 @11:16AM (#9157774)
It's risky, but it's not that risky. I'm sure freedom-hating, source-code-hoarding Apple has made the analysis that making Xcode work with copylefted git isn't going to make them reveal their source code. Back when Jobs got pwned by the GPL during his NeXT days, he probably vowed "never again", but that doesn't mean Apple has stopped shipping GPL'ed code.

If Apple can afford to use the GPL, i.e. they think the GPL risk is low enough for them and won't make them free their entire codebase, then anyone can also make this assessment.

Re:The time has come to stand up for the GPL by nemo on Friday March 06, 2015 @12:18PM (#9158180)
Apple has very steadily migrated away from using GPL. Every major release there are fewer and fewer GPL packages in their systems and they use old versions of tools to make sure they are still under GPLv2 - bash 3.2, rsync 2.6.9, etc, apparently out of fear of GPLv3. They are off gcc, they wrote their own SMB code to ditch Samba, and have gone out of their way to avoid GPL wherever possible.
Re:The time has come to stand up for the GPL by jordigh on Friday March 06, 2015 @12:31PM (#9158248)
They have their (imo, silly) reasons to dislike the GPL. Fear of having to release all of the source code for all of their products is not one of them.
Re:The time has come to stand up for the GPL by nemo on Friday March 06, 2015 @12:45PM (#9158335)
They have their reasons, but its hard for me to judge whether they're silly since they haven't made their legal analysis public or publicly explained why they've chosen the course they have.
Re:The time has come to stand up for the GPL by jordigh on Friday March 06, 2015 @12:59PM (#9158425)
During the GPLv3 draft phases, they publicly expressed concerns against the tivoisation clause, which is not at all surprising. Apple wants to keep some control over their users' devices.

They seem to have no problem with GPLv2, but since they are using the last and aging GPLv2 releases of a bunch of GNU packages, they seem to be moving to non-copyleft alternatives purely because there are no more updates to the GPLv2 versions.

They had no apparent problem in adding git to Xcode despite their overall GPLv2+GPLv3 purge.

Re:The time has come to stand up for the GPL by angersock on Friday March 06, 2015 @11:46AM (#9157981)
Jobs got pwned by the GPL during his NeXT day

That sounds like a fun story. What happened?

Re:The time has come to stand up for the GPL by jordigh on Friday March 06, 2015 @11:53AM (#9158017)

    Consider GNU Objective C. NeXT initially wanted to make this front
    end proprietary; they proposed to release it as .o files, and let
    users link them with the rest of GCC, thinking this might be a way
    around the GPL's requirements. But our lawyer said that this would
    not evade the requirements, that it was not allowed. And so they
    made the Objective C front end free software.
https://www.gnu.org/philosophy/pragmatic.html

    Specifically, as I've spoken about in my many talks on GPL
    compliance, the earliest publicly discussed major GPL violation
    was by NeXT computing when Steve Jobs attempted and failed (thanks
    to RMS' GPL enforcement work) to make the Objective C front-end to
    GCC proprietary. Everything for everyone involved would have gone
    quite differently if that enforcement effort had failed.
http://ebb.org/bkuhn/blog/2014/01/26/llvm.html
Re:The time has come to stand up for the GPL by legulere on Friday March 06, 2015 @12:24PM (#9158204)
And yet apple is basically responsible for creating the non-copyleft free objective c fronted for llvm. They could have just kept it closed source.
Re:The time has come to stand up for the GPL by jordigh on Friday March 06, 2015 @12:35PM (#9158286)
They're basically achieving their dream now with Swift, though. I don't expect them to ever release that source. I don't think there is any precedent for Apple releasing source code after the fact.
Re:The time has come to stand up for the GPL by foobarqux on Friday March 06, 2015 @12:11PM (#9158124)
> That uncertainty plus the viral nature of the GPL means that there's no way to know for sure that you won't be forced to open your whole codebase at some point in the future.

That doesn't happen. A violator would be ordered to pay compensation and remove the offending code, though they could reach a settlement to do something else.

Re:The time has come to stand up for the GPL by joshyeager on Friday March 06, 2015 @12:54PM (#9158393)
Ok, good point. But for a small- to mid-sized software company, a big fine or a big reengineering effort is pretty dangerous too.
Re:The time has come to stand up for the GPL by foobarqux on Friday March 06, 2015 @01:11PM (#9158497)
Sure, but the vast majority of GPL violations are no more surprising than "shared source" proprietary code: Using each imposes certain obligations and no one is confused about the latter, I don't know why so many people think GPL is some kind of trick designed to trap you, it's not.
Re:The time has come to stand up for the GPL by venomsnake on Friday March 06, 2015 @12:20PM (#9158187)
Is the GPL that toothless?
Re:The time has come to stand up for the GPL by kazinator on Friday March 06, 2015 @01:59PM (#9158787)
What would constitute having "teeth" for you? Mandatory jail terms even when parties are willing to settle? Execution by firing squad?
Re:The time has come to stand up for the GPL by venomsnake on Friday March 06, 2015 @02:22PM (#9158960)
Well C levels executives are the only persons I support unconditional death penalty for. But mandatory opening of all source code will be more valuable than money.
Re:The time has come to stand up for the GPL by foobarqux on Friday March 06, 2015 @01:03PM (#9158449)
That's the law, not GPL.
Re:The time has come to stand up for the GPL by kuschku on Friday March 06, 2015 @11:14AM (#9157761)
LGPL might be the best solution then (I personally would say LGPL should be used for everything, but that’s a personal opionion), because LGPL only goes viral through actual forking, but does not consider linking.
Re:The time has come to stand up for the GPL by halostatue on Friday March 06, 2015 @11:45AM (#9157974)
This is not quite correct. The “link wall” matters mostly in compiled languages, but consider a proprietary program Quux that links to the GNU LGPLed libhoge. When the owner of Quux distributes it, they must also (on request) provide recipients the source to libhoge and the ability for Quux to be relinked against a modified version of libhoge. They either have to be using libhoge.so or provide the object files and tools to link against a modified libhoge.a.

Simply providing the source of libhoge is not sufficient, and most people do not understand that about the GNU LGPL.

Re:The time has come to stand up for the GPL by jallmann on Friday March 06, 2015 @12:29PM (#9158236)
Linking is really not big a deal with LGPL, provided you're comfortable with the GPL. You might have to think a little harder if you're distributing statically, but given the goals of the LGPL and the technicalities of linking, its provisions are reasonable.

Yes, you have to provide the source and a build process for the (L)GPL'd software in question. That's standard for both the GPL and LGPL; no difference. From there, linking is just another step in the build with ld, or at runtime with LD_PRELOAD.

The LGPL is incredibly under-appreciated. Developers love to complain about GPL'd software, but who actually takes raw chunks of code, or entire applications, and re-packages it as their own? Most developers don't have a reason to do this -- the majority of our work with third-party code consists of interfacing with libraries and that is where the LGPL comes in handy.

If you're uncomfortable committing completely to the GPL but still want to support its basic tenets, try the LGPL.

Re:The time has come to stand up for the GPL by halostatue on Friday March 06, 2015 @02:34PM (#9159031)
This doesn’t really change the fundamental problem—most people think that all they have to do in order to be compliant with the GNU LGPL is release the (modified) source of the library under the GNU LGPL. The licence is (reasonably) clear that this is not the case, but this confusion is one of the reasons why it was renamed from the GNU Library GPL to the GNU Lesser GPL.

I personally recommend against using the GNU LGPL because of this confusion. If you want something that does what most people think the GNU LGPL does, use the MPL with a GNU GPL exception. (IMO, the MPL is a superior licence to anything in the GNU GPL family, but it is also not my licence of choice—that is the MIT-style licence.)

Re:The time has come to stand up for the GPL by jallmann on Friday March 06, 2015 @05:27PM (#9160003)
That's a problem with people, not with the LGPL. Would you sign a contract without reading it through? The same goes for software licenses. Suggesting an alternative license doesn't absolve people of the responsibility of reading the suggested text in the first place.

The language of most of common software licenses is straightforward; blindly using any license without being aware with their implications, especially in a commercial capacity, is... stupid.

Beyond that, we'll have to agree to disagree. If you're familiar with the four freedoms of the GNU free software definition [1], then licenses that are nonfree and non-copyleft do not ensure the four freedoms for users of the software. The (L)GPL has been carefully crafted to ensure those those freedoms. Although that might not matter to you personally, preserving those freedoms is important for many people.

[1] https://www.gnu.org/philosophy/free-sw.html

Re:The time has come to stand up for the GPL by nymisunderrated on Saturday March 07, 2015 @08:46PM (#9164083)
What is MPL with a GPL exception?
Re:The time has come to stand up for the GPL by halostatue on Sunday March 08, 2015 @12:19AM (#9164659)
That’s the Mozilla Public Licence. If I recall correctly, it is considered incompatible with the GNU GPL (although it probably shouldn’t be) without an explicit clause permitting combination of MPLed software with GNU GPLed software.

The MPL is a superb licence that is under-appreciated. It usually acts similar to the MIT licence in that it never taints your software that uses MPLed software. It has, at best, a “modular” taint. If you depend on an MPLed library, you can combine that library without revealing your source at all. If you modify that library, you only have to release your modified source. You can even modify it so that it goes from proprietary -> MPLed library -> proprietary, but you have to document the nature of what you’re doing in that call out from the MPL and you may need to release that (I haven’t dealt with the MPL in years, but I think that describes that particular case).

GNU activists were loud enough for years (despite having had the exact same debate at the beginning of the licensing project) that ultimately Mozilla caved and dual-licensed its projects just to shut them up. (It didn’t help with some folks in the Debian community because of the constraints on the trademarks, but some people will never be satisfied unless you’re receiving your web pages by email in emacs.)

Re:The time has come to stand up for the GPL by nymisunderrated on Sunday March 08, 2015 @09:09PM (#9168269)
Thank you. I asked because the expression "MPL with GPL exception" wasn't clear to me.

You may want to know that in the past few years, MPL 2.0 was released, which embeds a so-called "GPL compatibility" by default. In fact, it's a relicensing allowed by MPL 2.0 licensor.

MPL 2.0 still keeps an option for the licensor's software to never be relicensed, but they have to specifically use an "incompatibility" clause.

Re:The time has come to stand up for the GPL by vezzy-fnord on Friday March 06, 2015 @11:43AM (#9157954)
I'd actually recommend MPL instead, because it enforces copyleft on the source file level rather than the library level. This makes it unambiguously applicable to just about anything other than Smalltalk, whereas the LGPL's terminology is slanted towards C/++ semantics.