Category Archives: GPL

GPL v3: Yet Another Draft

The FSF has released yet another draft of the GPL v3 today. Needless to say, people are getting pretty frustrated by the lack of progress and difficulty in completing this update to the GPL. Steven J. Vaughan-Nichols on Linux-Watch considers how much longer it could possibly take: “Mid-2007? At least. Late 2007? Quite likely. 2008? Could be. 2010!? I wouldn’t be surprised. I’ve got a bad feeling about this.”

Allison Randal at O’Reilly is pretty skeptical, and I have to admit that I have heard similar skepticism from others, including many who have been strong supporters of the FSF for years:

“I will say this much: I’m a believer in free software, and in the importance of free software in advancing the freedoms of individuals. But I’m beginning to lose confidence in the FSF as the primary defender of free software principles. The image they’re projecting right now is more of an ineffectual nanny slapping the wrists of naughty children than it is of the bold community leader confidently striding on to the visionary future of the free software movement. It’s unfortunate. Maybe we’ll see change in this draft and the next. Maybe. (Quote from Allison Randal on the O’Reilly Radar)

At one point, I was following the changes and keeping up with the progress toward GPL v3, but I have to admit that toward the end of last year I gave up. I’ll read the final version if they ever manage to complete it.

Second Life Moves to Open Source

Second Life has just announced that the Second Life client has been released under an open source license, and they described their move to open source as “inevitable”:

“At Linden, we have always been strong advocates of the use of open standards and the advantages of using open source products. Though Second Life makes abundant use of non-standard technologies, our basic UDP protocol message system for example, we rely on open standards and open source implementations when appropriate and available. Since many of the components that will make up this network are not yet done, we are not publishing long white papers or RFCs at this time — instead, we are giving everyone what we have along with a goal of producing those open standards with the input and assistance of the community that has brought Second Life to where it is now.

Releasing the source now is our next invitation to the world to help build this global space for communication, business, and entertainment. We are eager to work with the community and businesses to further our vision of our space.” (Quote from the Second Life Blog)

I also found it interesting that Linden Lab specified the GNU GPL version 2, rather than releasing it under the GPL and future versions … another company hedging its bets on the still under development GPL v3.

I think this is a great move for Linden Lab, and an astute business decision. By releasing the client software under open source, residents can modify their client experience, while Linden Lab continues to provide the server side code, which is where they make their revenue. Linden Lab is providing a more flexible environment for users, which should translate to additional users, and at the same time, they continue to have the revenue stream required to keep Second Life in business.

MySQL Hedges Bets on GPL

MySQL “kind of sort of (not really) changes its license model”. Until recently, MySQL was licensed under GPLv2 or later, but they have changed their license to be GPLv2 only. This may sound like a small change, but it is a significant (and smart change). Anyone licensed under GPLv2 or later will automatically convert to the GPLv3 when it is released. This gives MySQL the option to decide whether (or not) to move to the GPLv3, instead of automatically converting upon release of GPLv3. MySQL will have the opportunity to review the final version of the GPLv3 license and make an informed decision about which license makes the most sense for MySQL’s business needs.

Not every company (or project / organization) can change their license at will:

MySQL owns the copyright to its database code so can change the license any time it likes (and indeed offer the software under dual licenses). While the company is not ruling out a change to GPL v3 once it is completed, it is hedging its bets in case it does not like the results.” (Quote from Matthew Aslett on Computer Business Review Online)

OSDL Shake-up: Reduces Staff by 1/3 and Stuart Cohen Leaves

The Open Source Development Labs (OSDL) in Beaverton, OR has just eliminated 9 technical and administrative positions at the labs. A staff of 19 people remain at OSDL including Tom Hanrahan in engineering, Diane Peters for legal work, Linus Torvalds, and Andrew Morton.

ZDnet writes that “CEO Stuart Cohen resigned to pursue opportunities with higher-level open-source software,” and that “Cohen’s resignation as CEO was coincidental and independent of the other changes at OSDL”. According to ComputerWorld, Cohen will be working with Portland and Seattle based venture capital firm OVP Venture Partners. Mike Temple will be moving the COO position into the CEO role.

The now smaller OSDL will focus on the following:

“The lab’s board concluded that a modified mission was appropriate because Linux is now mainstream, and companies have become adept on their own at some of the collaborative work OSDL was founded to oversee, Temple said Monday. The group is funded by IBM, Hewlett-Packard, Novell, Intel and several other computing companies.

OSDL’s middleman role–connecting customer requirements, computing-company resources and developers–remains unchanged, Temple said. “We will be a catalyst among those three, to bring them together, solve problems and create the code,” Temple said.

Funding freed up through the layoffs is set to go toward legal work, which the group’s members have found valuable, Temple added. The group either will contract with legal professionals or hire a staff attorney, he said.

In technical matters, the organization will stop focusing on projects defining broad categories of Linux–earlier examples including efforts for high-end servers, telecommunications gear, mobile phones and desktop computers. Instead, engineering work will emphasize narrower efforts to find areas where new software needs to be written.” (Quote from Zdnet)


“The OSDL is shifting its resources to focus on four key areas: continuing to provide a safe haven for key developers, sponsoring the work of Torvalds and others; providing increased legal support for Linux and open source to account for licensing and patent issues that are increasing in complexity (this expansion will complement current OSDL initiatives such as the Patent Commons, Osapa.org and the Linux Legal Defense Fund); supporting ongoing regional activities such as the Japanese Linux Symposium; and fostering closer collaboration among community developers, OSDL members and users to produce more code to advance open-source projects, OSDL officials said in a statement.” (Quote from eWeek)

Here is my take on the situation. I do not buy the “coincidence” argument. I find it very hard to believe that the CEO of any organization would just decide, completely of his own accord, to leave during a change of this magnitude. With a staff reduction of this relative size combined with a new strategic direction, Cohen’s leaving OSDL would not have been a coincidence. There are a few possibilities (caveat: this is pure speculation):

  • First, the board of directors may have “suggested” that Cohen leave due to any number of potential issues: dissatisfaction with his performance, lack of confidence in his ability to lead the organization under the new mission, …

  • Second, Cohen may not have wanted to stay under the new mission for any number of reasons: lack of agreement with the strategic change and new mission, expecting the job to be less exciting under the new mission and wanting to find greener pastures, …

Despite my skepticism about Cohen’s “coincidental” leaving, I do think that the new mission will be good for OSDL and for Linux. When OSDL was first formed, Linux as an open source project was less mature, and fewer contributors to the Linux kernel were sponsored by large companies who paid their salaries. As a result, the contributions tended to be made in areas of personal interest, which may or may not have been the areas needed to make Linux successful in large deployments of mission critical systems. OSDL helped to coordinate efforts and provide testing labs where Linux could be tested on large clustered systems not generally available to most people. Now, with companies like IBM and Intel doing more work toward sponsoring developers and helping with testing, OSDL’s original mission has become less important.

The focus on legal matters makes sense. With the proliferation of lawsuits, concerns over software patents, licensing concerns and other legal matters becoming top of mind, having an organization to focus on open source legal issues could be a great benefit. 2007 could be an interesting year for open source legal matters: the GPL is undergoing a revision, and the Microsoft / Novell agreements related to patents could be clarified. Many open source projects are run by small groups of individuals or small companies, and it would be great to have OSDL as a legal resource.

The GPL and Antitrust Law

A U.S. court has found that open source software provided free of charge under the GPL does not violate antitrust laws … or as Matt Asay says “Duh!”. An excerpt from Evan Brown’s Internet Cases blog provides a nice overview:

The U.S. Court of Appeals for the Seventh Circuit has issued an opinion in which Judge Easterbrook declares, “[t]he GPL and open-source have nothing to fear from the antitrust laws.” The case is called Wallace v. IBM., No. 06-2454. [Download a copy of the opinion.] Internet Cases covered the lower court’s decision from last December here.

Plaintiff Wallace filed an antitrust suit against IBM, Red Hat and Novell, arguing that those companies had conspired to eliminate competition in the operating system market by making Linux available at an “unbeatable” price (free) under the General Public License (“GPL”). The U.S. District Court for the Southern District of Indiana dismissed the case, finding the plaintiff had suffered no antitrust injury. The Seventh Circuit affirmed.