Slashdot Mirror
Apache says ASL2.0 is GPL-compatible
Steve Loughran writes "The ASF board have put up on the Apache Web site, a page
rebutting claims that the new ASL2.0 license is incompatible with the GPL, claims made by on an
FSF page and covered in
Slashdot last week.The key points are (1) The interpretation of the GPL license is not just the opinions of individuals in the FSF, it is designed to be rigorously defendable in a court of law.
(2) Rather than look at opinions about compatibility, people should look at the
ASF2.0 and GPL licenses to see if they really are compatible.
(3) If you look at the two licenses, they really are compatible.
This means there is nothing to stop you linking your [L]GPL apps against apache libraries, shipping them with apache applications, and the like." Of course, this is still up to debate.
You just know that the author of the Apache rebuttal page wanted to end his analysis with: "So get bent."
Apache is a pretty good piece of software and if folks don't like the new license, well that's just tough. They have a right to license their code however they choose to. The people who write to them and tell them otherwise really do need to drop off the planet.
-sirket
... Is an ignorant statement. Some authors decide to release their code under a certain license, and people bitch. If ASL doesn't play nice with the GPL, that is unfortunate... and we might have to look at something else. Then again, Apache 1.x is working great as far as I can tell. But these license zealots whining about how the "BSD/ASL/XFree/GPL sucks" are really just ignorant. If I write some code, and don't want it to be sucked up by a profit-making corporation without my consent, and without recieving any credit, that's my own fucking business! By the same token, if I want my code to be able to be used by whomever wants it, again, that's my own fucking business!
The ASF statement actually is really useful, because in essence they are saying they think its GPL compatible, so there are no issues on their side.
Its irrelevant however because Apache is built upon a set of non GPL compliant libraries like OpenSSL and always has been. "Apache 2.0 not GPL", well big deal: Apache 1.0 not GPL either.
You can probably build a non https:// Apache without a few other modules that is GPLable but everyone I've dealt with seems quite happy with the state of apache and the license it uses right now.
This is very different to the XFree 4.4 case where the rules got changed on people.
Its very much like "Windows 98 not GPL".. not news.
Unfortunately distributing non-GPLd software with Linux is asking for trouble. Linux is the best-selling open software product and choosing any other license than GPL means an extra hurdle for your software.
... so that more people, including those who chose to release their software under the GPL, can make use of their code (which is the primary interest of the BSD folks).
What a load of absolute crap.
There is absolutely no problem distributing non-GPLed software (even proprietary software) with Linux. Just because the kernel is GPLed doesn't mean the software which runs under it must also be GPLed. glibc is LGPLed (ie. you can link non-GPLed and proprietary software against it), asn are nearly all of the core libraries.
Oracle ships with Linux, and it is proprietary. XFree (pre 4.4) ships with Linux, and has (had) a BSD-ish (but GPL compatible) license. Openssh ships with Linux and has a BSD license. And this list goes on.
There is absolutely no issue whatsoever in distributing non-GPLed software with a GPLed operating system.
There is an issue with combining code from non-GPLed products and GPLed products into a new product, which is why XFree 4.4 is going the way of the Dodo, with virtually every distribution under the sun sticking with 4.3 or going with one of the forks (freedesktop.org or what have you), but that is a result of the amount of GPLed software linked to X libraries no one is willing to give up, not a result of the Linux operating system.
This is why Apache is working toward a GPL-compatable license, and why the FreeBSD folks went through the effort they did to make their license GPL compatible
And yes, this is the kind of Freedom RMS and others, such as myself, like: the freedom to chose the license we prefer for our code, which for many of us is a "share-alike" license such as the GPL.
And the results speak for themselves: the first viable competitor to go up against Microsoft in a generation (Linux), thousands of free software projects where the code is guaranteed to remain free in perpetuity, and widespread cooperation between two philosophical camps despite differing opinions on where to emphasize the freedom (developers a la the BSD, vs. users a la the GPL), rabblerousing from the proprietary sidelines via agent provocateurs, and their less intelligent cousins, trolls such as yourself, notwithstanding.
The Future of Human Evolution: Autonomy
In this particular instance I agree with Linus. However, it is very annoying that whenever there is an argument some one always posts Linus' opinion and presents it as THE ANSWER. He's just one famous nerd. Nothing more. You know what the buddists say.. If you meet Buddha waking down the road Kill Him. He will only be a distraction on your road to enlightement.
Well.. maybe. Or Maybe not. But Definitely not sort of.