December 23, 2004 4:00 AM PST
Sprucing up open source's GPL foundation
- Related Stories
-
IDC: Linux PC sales to hit $10 billion in 2008
December 15, 2004 -
Sun open-source license could mean Solaris-Linux barrier
December 2, 2004 -
Firefox cutting into IE's lead
November 22, 2004 -
SpamAssassin sports new open-source license
September 22, 2004 -
IBM pledges no patent attacks against Linux
August 4, 2004 -
Group: Linux potentially infringes 283 patents
August 1, 2004 -
Red Hat adds legal firepower
May 17, 2004 -
Attorney: More disclosure will end GPL case
April 23, 2004 -
GPL gains clout in German legal case
April 22, 2004 -
MySQL takes cue from the master
April 14, 2004 -
The greening of Linux
December 3, 2003 -
SCO attacks open-source foundation
October 28, 2003 -
Gates wades into open-source debate
June 19, 2001 -
Netscape now--for free
January 22, 1998
GPL author Richard Stallman said he's working on amendments that could deal better with software patents; clarify how GPL software may be used in some networked environments and on carefully controlled hardware; and lower some barriers that today prevent the mixing of software covered by the GPL and other licenses.
In the 13 years since the current GPL version 2 was released, the license has moved from the fringes to the center of the computing industry. GPL software is now common at Fortune 500 companies and endorsed by most large computing firms. But that prominence has made some eager for an update.
What's new:
The General Public License, the legal foundation for free and open-source software movements' collaborative philosophy, is being modernized to deal with new realities in the software realm.
Bottom line:
Observers believe the GPL could be improved to better deal with a world that involves patent lawsuits, locked-down hardware and publicly available Web services--all items on the GPL agenda.
"The GPL has become the pivot point of a multibillion-dollar industry. Frankly, I don't think it was designed for that," said Mark Radcliffe, an attorney with Gray Cary who has studied the GPL and other licenses extensively.
For example, some would like to see clarifications that could help reduce the threat that using GPL software could entangle users in patent litigation. And the GPL could be better adapted to recent industry initiatives such as building sophisticated Web services on the Internet and boosting security through trusted computing methods.
Ordinarily only attorneys give much thought to the legal documents that govern how software may be used. But the GPL is different.
The license is the agreement that helped show that cooperation can work in an industry dominated by competition. And the most persuasive illustration of its power is Linux, a rising threat to computing giants such as Microsoft and Sun Microsystems.
The GPL governs the programming instructions called source code that developers write and then convert into the binary files that computers understand. At its heart, the GPL permits anyone to see, modify and redistribute that source code, as long as they make changes available publicly and license them under the GPL. That contrasts with some licenses used in open-source projects that permit source code to be made proprietary.Another requirement is that GPL software may be tightly integrated only with other software that also is governed by the GPL. That provision helps to create a growing pool of GPL software, but it's also spurred some to label the license "viral," raising the specter that the inadvertent or surreptitious inclusion of GPL code in a proprietary product would require the release of all source code under the GPL. Gates in particular derided the license as "Pac Man-like," evoking an image of a GPL software module gobbling its way along and forcing the release of source code it touches.
Thus far, that scenario hasn't come to pass. The GPL, though, has threatened Microsoft in another way: It helped foster a vast, vibrant programming community.
Microsoft is keenly watching the arrival of the new GPL, which Stallman said likely will be labeled version 3. But the company probably won't see changes to that core provision separating GPL and proprietary code.
"Overall it's going to be the same," the globe-trotting Stallman said in a telephone interview from Morocco. "I don't expect anyone releasing
See more CNET content tagged:
GPL,
Trusted Computing,
license,
Richard Stallman,
source code
http://www.groklaw.net/article.php?story=20031214210634851
The summary is as follows:
If someone uses GPLed code in their proprietary code and then distributes either the source or the binary (compiled from that code) without complying with the provisions of the GPL, they are in violation of the copyright of the GPLed software (since they don't have any permission to distribute GPLed code apart from the GPL). At no point would the owner of the proprietary code be forced to release their own work under the GPL (or any other license), though they could *choose* to do so in order to avoid a Copyright-infringement lawsuit.
This single power gives the GPL a license to change, and offers unforseeable protections, opportunities and reward for those using code covered by any version of the GPL.
No other license in mainstream use allows the anyone to distribute code with a freedom of choice over licenses in this manner.
"These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works."
The only way that the Microsoft code could become GPL licensed is if they re-write the DLL and then that DLL's code would be GPL. This would mean Microsoft would have to use code derived from copyrighted code, and that's theft and copyright infringement. So a claim of "virul nature" could only mean Microsoft wants to copy GPL code as it's own.
The short answer is that code is covered by the version specified with the covered software or any future version at the licensees choice. The licensee being the person provided with a license to copy, modify and distribute the code.
This is one of the most important and least emphasised portions of the GPL. It is a license to change the license at YOUR choosing. So when GPL 3.0 comes out, all previously covered GPL code is now also available under the new version of the license.
Here is the section verbatim from the GPL 2.0 -
"Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation."
I believe that this confuses PCT (Patent, Copyright, Trademark and related rights) protection with a very narrow political agenda known as the "maximalist agenda". This ideology suggests that "if some PCT is good, then more is better".
The reality is that PCTs are to creativity and innovation like water is to humans: too little and you dehydrate and die, and too much and you drown and die.
Believing that pouring water on a drowning person is good for that persons health is about as logical as suggesting that the maximalist ideology is a promotion of the public policy goals of patents.
Russell McOrmond
Information/mental process patents http://www.digital-copyright.ca/taxonomy/page/or/360