Is GPL Licensing In Decline?
GMGruman writes "Simon Phipps writes, "As Apache licenses proliferate, two warring camps have formed over whether the GPL is or isn't falling out of favor in favor of the Apache License." But as he explores the issues on both sides, he shows how the binary thinking on the issue is misplaced, and that the truth is more nuanced, with Apache License gaining in commercially focused efforts but GPL appearing to increase in software-freedom-oriented efforts. In other words, it depends on the style of open source."
Didn't we have this story last week?
Is Simon Phipps moonlighting for Ric Romero now?
Like it or not, but the fact that GPL is prohibited in many app stores is probably what discourages authors of FLOSS from using it as their license. Some authors may also feel that they don't want to use it even if it works fine for them now since they don't know what will happen in the future, as contributions are accepted from other authors it becomes much harder to change license. It's not 1991 anymore.
I've had recent occasion to talk to a few SAAS providers and other software producers who are employing OSS tech in some of their products and the consensus was the GPL was too constrictive, so their using other schemes. I'm also noticing others around the web sticking to GPL 2.0, and dismissing 3.0. I'm just a messenger, just what I've seen.
Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
to start a holy war on the subject. Both are open licences, so who cares?
The Metasploit Framework, for instance, only accepts code licensed with BSD (or BSD compatible).
GPL is still the most popular Copyleft license.
People that keep pushing that the GPL is loosing market share tend to be the ones that want to push open source in favor of the ideals of Copyleft and Free Software. The GPL is not designed to win the popularity war for people that refuse the ideals of Free Software in favor of open source. The majority of licenses accepted by the OSI should really be called Closing Source as several of those licenses allows anyone to modify or redistribute the code without the source code. Only a Copyleft license is designed to keep the software under Free terms.
Personally, I prefer the BSD licenses. There's more freedom in it. Although, I can see why people like the GPL & Apache licenses, I think they're a little too restrictive.
Who'd a thunk it?
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
Personally, I think the whole open source gig is fading away. The next generation of programmers have been raised to live and program in flashy iDink walled gardens and have neither the interest or the inclination in releasing or collaborating on code.
In their world, code is something that is packaged into an app, approved by Apple, and then sold for profit. It is not something which can even be freely compiled and run on their devices, let alone shared and co-written.
Ultimately computers and the Internet are growing up, moving out into suburbia, and accepting pre-packaged convenience over creative potential. People want shiny and slick, and really couldn't care less freedom, code, control, or innovation. There's probably an App for feelings like that anyway.
The Internet is becoming squaresville, one settled Mac user at a time.
May the Maths Be with you!
Apache licenses are favoured by projects which have corporate sponsorship and funding.
GPL licenses are favoured by "grass roots" efforts which have no funding.
The question is the funding a cause or an effect of the choice of license?
I do not fail; I succeed at finding out what does not work.
(I know TFT is a dupe post, but I'll post my comments anyway)
I do a lot of open-source. Most of my projects are either extremely small, small, or mid-range. Those projects are broad, ranging from small functions to small libraries, to full working applications and to full working systems. Some of those projects are indeed appreciated, but so far I can tell you that less than 1% of the code (either software, or HDL) came from third parties. So, people are likely to use, but less likely to contribute (most of them do not have the knowledge to contribute, so only a small part can effectively do it).
But why do so ?
Let me just make an overview here, we'll get to GPL later.
A few things can happen to an open-source project:
a) People love it, they are hackers, they want to improve it, you're a nice guy, they contribute. All thing gets merged in.
b) People love it, they don't know how to program, they want to improve it but don't have the means. They provide important feedback.
c) People love it, they hate you, they fork your project and follow like a).
d) People don't like it, or just ignore it, you're off. Nothing to see here.
So, how are you to license a project of your own ? If you go closed source (freeware, shareware) you get b) and d). Indeed these are the most common.
If you go open-source, chances are you get d) and b). Only in very specific situations you get a).
So, why would you release your project as GPL ? Why not Apache licenses, why not CC, why not BSD ?
That will depend on your expectations, and whether you allow commercial use (mean, give it *really* away for free without any reserve)
I don't recommend GPL unless for a), which indeed is the most uncommon. If indeed your project becomes popular, c) is going to happen. GPL is nice for community-based projects, it's not that nice for personal projects, because you either lose control of it (others fork it if they dislike you) or you don't have contributions at all.
I still use GPL for some of my projects (software), but not for hardware ones (I use BSD).
If you're starting a new project, think twice - although remember it's your own work - if no one contributes to your "mainline", you can change it's license at your own will (but previously released versions will keep the license in which they were released).
Also, GPL became so complex that people avoid using it. BSD and variants are easier to read and understand.
Alvie
To restate the obvious:
There are two paradoxical possible twists to an open source license.
1. The user is allowed to use the source as part of a closed source product (which is a kind of freedom)
2. The user is obliged to make derivatives available as source (which ensures the greater freedom of other users/developers) (this is a restriction on the actions of user 1)
Neither one is complete freedom. They are both giving up something - the possible work of the downstream user or the business motivation of the first user.
The GPL's origin is in RMS' desire to be able to modify software that was produced by companies. It takes this to the extreme, basically by prohibiting closed source products based on GPL.
The benefit of this is mostly to developers, and within that, to developers who are independent. Software companies share code / secrets a lot as part of business, but under NDAs. The FSF has as a slogan "you deserve software that is free" but how many users want to exercise the freedom to modify and recompile their software?
More and more, FOSS is produced in a dual stream approach - Redhat/Fedora, Jboss community/pro, other things work this way like Jasper reports etc
The reality of this is that the code that is run in production is not "free" in an active way. When you pay for a supported version of RHEL or whatever you do not generally modify anything very deep inside it and then demand support for your modified version. The fact that you are paying for a supported version is a disincentive to using a modifed version, your own or anyone else's.
Also consider that the Linux kernel is largely developed by people working for IBM, Suse, Redhat, etc.
So while the lone developer wanting to add his improvements to the commercially produced and defective printer driver is a convincing story to argue for the GPL, the reality as it is today is different - it's more like the millions of Linux users who wish their hardware was supported but do not produce a driver for it. And I know they may not have access to the necessary information from the hardware maker, etc. Still, the number of people able and motivated to write OS-level code is small. I know I don't know enough to do it.
Nonetheless, the existence of (mostly) GPL OSes is an amazing thing. The access to knowledge for developers that that provides is awesome. But a lot of the requirements to stay GPL-pure do not sound like freedoms to me- requiring you not to buy certain(most) products, visit certain sites - it's ironic when, in the name of freedom, your freedom to act as you wish must be limited.
You ask me: "Is GPL Licensing In Decline?"
I ask you: "Who Cares?"
if the GPL fits your goals (personal, business, etc.), then use it.
If the GPL doesn't fit your goals, then don't use it.
If the whole world goes GPL or I am the last person on Earth releasing code under the GPL license .. does it really matter, if we're all meeting our goals?
Of course, any library published with a restrictive license (GPL) will eventually be supplanted by a library with a more liberal license (BSD, etc)
The value proposition is simply better.
If Pandora's box is destined to be opened, *I* want to be the one to open it.
Many banks and other companies that received threatening letters from SCO and MS salesmen have anti gnu or freeware policies in their organization. A famous Canadian bank even licenses for an obsolete version of SSH because BSD *might* be gnu. Funny, that the corporation just downloads the BSD one and repackages to the customer as its own for $$$.
Lawyers are afraid of it in big companies after several court cases with companies like Netgear being accused of copyright infringement for including Linux without the source in some of their embedded products.
I could turn this into a BSD vs GPL flameware but wont. There are many such as myself who feel comfortable using free software at work but would feel better modifying and shipping BSD versions which are more business friendly to customers and suppliers. Remember you are asking the company to ship its crown jewels away if they license it with GPL. It is true it may protect you agaisn't getting ripped off, but you have no way to know for sure.
Businesses do not like risk or to give away free things. They own them if they paid for the labor so why the risk?
http://saveie6.com/
The thing is, what coders wanted most of all was for people to use their code. They felt that under the GPL they'd also encourage other people to share. Instead it put people off using their code.
Other licences still don't allow people to close the existing code. Only the changes. Many companies who want to hang on to a few of their proprietary modifications of code are still often happy to give back something to the community so a more liberal licence will actually encourage more development.
No.
Whoops you just showed how ignorant you are of copyright law. If some intern puts in GPL code into your app, and you don't wish to GPL your app, then you are in a copyright violation situation. At this point you are liable for damages. But this would be the same situation as when your intern puts in code from any other unauthorized and unlicensed source. You have 3 options, after settling the damages part: 1. Remove the offending code. 2. GPL the rest of the code so as to comply with the license, or 3. purchase a commercial license for the offending code in terms you negotiate that are better for you.
Please stop streaming the lie that GPL can magically infect your proprietary code. It's companies that lie and then get caught that end up in a world of hurt when they've shipped out a product with thousands of units and then find themselves in a copyright violation situation. At that point I have no sympathy for them. They know the law, and they know that copyright gives them zero access to other peoples' code, except under license from the copyright holder.
"my brother .. insisting that .. Linux doesn't have a stable ABI and API", Crosshair84
I hadn't realized that Linux doesn't have a stable ABI and API. Please explain how this negatively affects its performance on the desktop and in server space.
AccountKiller
"GPL is prohibited in many app stores"
Which apps stores prohibit GPL software and what reasons do they provide?
AccountKiller
Linux does very much have an API - that's not the problem. The ABI part - it's important when it's a question of having Linux (or any OS) recognized by the hardware that it needs to use - be it the sound, the wi-fi, the printer and any other hardware that needs to be accessed. Problem in Linux is that different versions of drivers work only w/ particular versions of the OS - you cannot mix and match driver versions and kernel versions. I found that out the hard way on Linux - I found an ALSA driver that would work w/ my RHEL5. Later, when that file system crapped on me and died and I had to do a re-install, I decided to install a different RHEL based distro, which had a few more software titles I was interested in. Getting the sound to work here was problematic - the ALSA version that I had did not work, and I had to, through trial and error, find the one that did. The sound quality was mediocre.
An ABI would have ensured that any driver written to it would work on any version of Linux (okay, I'll be reasonable and not insist that it works from Linux 1.0 to 2.0, but when it has problems b/w 2.1 and 2.3, that's unacceptable.) Otherwise, one has, what - some 17 revisions of the linux kernel times 9 revisions of ALSA, which would be what - some 150 different combinations one would have to try out? Who in the world has the time for all that?
This was just the sound - now, repeat the same exercise for Wi-Fi (which one has to have if one is going to go online to download anything that Linux advocates suggest getting in order to have one's system working. I never had Wi-Fi working w/ any of my Linux distros. I've pretty much given up on Linux, and would be trying out PC-BSD whenever I get it.
Yeah, and it's time to discuss something new. I didn't submit the following story, since it's now a month old, but I did find it interesting that Debian, which has always spoken the language of Free Software, decided to join the OSI.
Why? Debian itself has what it calls its 'Free software guidelines', and in it, Debian follows pretty much the same language as the FSF. However, the FSF refuses to recognize Debian as free software. Why? B'cos Debian 'also provides a repository of nonfree software. According to the project, this software is “not part of the Debian system,” but the repository is hosted on many of the project's main servers, and people can readily learn about these nonfree packages by browsing Debian's online package database.'
In other words, b'cos Debian decides to give its users the choice of using 'non-Free' software if they want to, the FSF blacklists them and doesn't endorse their distro. I fully agree w/ Hairy and Barbara above that this is a religion, and nothing illustrates my point better than this. It's not enought that an organization provide 'the community' w/ 'free software' - it's also necessary that they not provide anyone - not even those who want it - w/ non-Free software. This is what makes the FSF a bunch of fanatics who sane people would avoid.
Debian has done a good first step in joining OSI - something that IMO they should have done many moons ago. Next thing I hope they do is substitute the deceptive term 'free software' w/ 'open-source' wherever they can. Like they say in the announcement, they needn't embrace every license that the OSI has accepted as Open-Source, but at least, by being more business friendly than the FSF, and using more industry accepted terminology, they can get more monetary backing for Debian from the industry.
So, Apple are great because, to allow coders using Ruby to code their stuff to use Apple products, they write a ruby port.
Yeah.
Darwin Streaming Server? Ever heard of VLC? Another lock-in.
Remember, GPL2 doesn't specifically cite GPL licensing of patents. As to the other stuff? Never once heard of it.
Have you heard of CUPS? KHTML?
Why would anyone use GPL? A much better license is [license name]. It is obvious to anyone that the advantages include [arbitrary reasons]. In fact, [ad hominem]. When I was faced with this situation, I [irrelevant anecdote].
--
Vote Ron Paul, because [thinly veiled "I said so"].
Not this shit again. How many times are going to have the same article over and over and over? Can we just move on please? This is getting stupid.
But... the future refused to change.
From an earlier Slashdot post:
http://linux.slashdot.org/story/12/03/03/142229/gpl-copyleft-on-the-rise
"Is Copyleft Being Framed?"
As we've seen something like 5 Slashdot posts based one 1 study, I would say that there is substantial evidence that the answer is "yes".
Yeah, it's true.