| Last of the GPL licenses goes to Version 3 |
Nov. 19, 2007
The Free Software Foundation published the GNU Affero General Public License Version 3 on Nov. 19. This new license, based on the GPLv3, enables those who use AGPLv3 software over a network to receive the source code for that software.
The AGPL was created to deal with the so-called ASP (application service provider) loophole in the GPLv2. When the GPLv2 was created in 1991, no one was concerned with the possibilities of SAAS (software as a service). Software was distributed by floppy disks or tape, and no one ran applications over the Internet.
So, the GPLv2 didn't deal with this concept at all. The loophole was that some people took the GPLv2 to mean that they could use open-source software to provide software services without granting people the right to access the source code. To cover this loophole, Affero, an online company that provides rating and reputation services for online volunteers, asked the FSF in 2000 to help it create a license that would let it distribute its code, while preventing other companies from taking the code, using it and hiding it within their corporate IT departments.
With the approval of the GPLv3, the AGPL was also incorporated, but that version was oriented toward papering over the ASP loophole. This new version makes it explicit that developers can use GPLv3 and AGPLv3 code in common projects. By publishing this license, the FSF aims to foster user and development communities around network-oriented free software.
By itself, the GPLv3 allows people to modify the software they receive and share those modified versions with others, as long as they make the source code available to the recipients when they do so. However, a user can modify the software and run the modified version on a network server without releasing it. Since use of the server does not imply that people can download a copy of the program, this means the modifications may never be released. Many programmers choose to use the GPL to cultivate community development, but if many of the modifications developed by the programs users are never released, this defeats the community-building aspect of the GPL.
As the AGPL addresses these concerns, the FSF recommends that people consider using the GNU AGPL for any software which will commonly be run over a network.
The new versions of both licenses also explicitly allow developers working on a project under one license to combine it with code released under the other. For example, programmers who want to use the GNU AGPL for their own work can use any of the many libraries and other source files available under GPLv3. Developers working on GPLv3-covered projects will be able to use modules under the GNU AGPL with minimal hassle as well, since the GNU AGPL's additional term has no requirements for software that doesn't interact with users over a network.
FSF board member Benjamin Mako Hill explained in a statement, "The GNU GPL has been the most successful free software license because it makes a program's source available to its users. This enables massive collaboration between developers, since everyone gets the same benefits from this rule. The GNU AGPL will enable the same kind of cooperation around Web services and other networked software."
"The GNU AGPL is very much a community license," said Peter Brown, the FSF's executive director. "The feedback we received while working on GPLv3 demonstrated a clear desire for this sort of license. And thanks to the community's help during the drafting, we're happy that the GNU AGPL meets those needs."
The new license is published on the FSF Web site.
-- Steven J. Vaughan-Nichols
Do you have comments on this story?
Talkback here
NOTE: Please post your comments regarding our articles using the above link. Be sure to use this article's title as the "Subject" in your posts. Before you create a new thread, please check to see if a discussion thread is already running on the article you plan to comment on. Thanks!
Related Stories:
(Click here for further information)
|
|
|
7 Advantages of D2D Backup
For decades, tape has been the backup medium of choice. But, now, disk-to-disk (D2D) backup is gaining in favor. Learn why you should make the move in this whitepaper.
4 Legal Reasons to Control Internet Access
The Internet is obviously a valuable resource for many organizations. However, many are exposed to legal liability concerns because they fail to control Internet access. Learn if you're safe in this white paper.
Rapidly Resolve J2EE Application Problems
Whether you are in the process of building J2EE applications or have J2EE applications already running in production, you must ensure that they deliver the expected ROI. Learn how in this white paper.
Load Testing 2.0 for Web 2.0
There are many unknowns in stress testing Web 2.0 applications. Find out how to test the performance of Web 2.0 in this white paper.
Build Better Games Online
For the game infrastructure providers, life is complex. Making money from games has become more complicated. Why? Find out in this white paper.
Building a Virtual Infrastructure from Servers to Storage
This white paper discusses the virtual storage solutions that reduce cost, increase storage utilization, and address the challenges of backing up and restoring Server environments.
Gaining Faster Wireless Connections with WiMAX
Welcome to what is quickly becoming the hyperconnected world where anything that would benefit from being connected to the network will be connected. Learn more in this white paper.
Is Your Desktop a Security Threat?
The new wave of sophisticated crimeware not only targets specific companies, but also targets desktops and laptops as backdoor entryways into those business’ operations and resources. Learn how to stay safe in this white paper.
Increasing SAN Reliability by 100 Percent
Storage area networks (SAN) are a strong part of storage plans. Learn how to increase your reliability and uptime by 100 percent in this case study.
|
|
|
|
|
news feed