• On ZDNet: Why not take the Linux plunge?
November 14, 2007 6:29 AM PST

Revoking open source

by Gordon Haff
  • Font size
  • Print
  • 2 comments

Those of us who have actually read through many of the Open Source licenses and have spent a fair bit of time mulling and discussing their consequences take a lot of things for granted.

One of those things is that once a program, or anything else, is released under an Open Source license you can't just take it back. Maybe this seems obvious to you, or maybe not, but it isn't to everyone. Perhaps especially as we depart the realm of software where most developers involved with Open Source have given at least passing thought to the implications of the GPL and other such licenses.

This was brought home to me the other week in this comment on Flickr by Lane Hartwell (username "fetching"). (The context isn't especially relevant to this discussion; I suggest reading the whole heated thread if you're really interested.) "[this discussion] has brought attention to some issues and may help change things on both ends. Who knew that CC Licenses were permanent? Flickr sure doesn't tell you when you choose that option."

There are a variety of of issues raised in this case, but the one I want to focus on is that a photographer initially posted a picture on Flickr under a Creative Commons license and subsequently changed its license to the default "All rights reserved" (i.e., any use beyond that allowed by Fair Use requires the explicit permission of the photographer). There is a family of Creative Commons licenses. They vary, essentially, in whether the licensed work can be altered and whether it can be used for commercial purposes. However, for our purposes here, we can just think of all of them as "Open Source licenses."

Physical world intuition might suggest that of course the copyright holder, the owner of the property in a sense, can unshare a work anytime he or she chooses. If I give you permission to borrow my car, I can certainly give you permission on a one-time basis or can withdraw that permission at any time (subject to any contractual agreements).

But Open Source licenses are different. Once I put a photograph, a novel, or a program out in the world under an Open Source license, it's out there. I can't go "never mind" and withdraw whatever rights the license granted in the first place.

I'm not saying that the copyright owner can't change the license. In the case of works to which multiple people have contributed, there are a variety of complications and legal theories around changing licenses, but that's a separate issue. The bits or the words or the arrangement of ink droplets that have already been released into the world remain covered by the Open Source license they were originally released under.

A Mattel court case involving their CyberPatrol software and a program by Eddy Jahnsson and Matthew Skala called cphack raised the issue of whether a GPL license could be withdrawn. However, the case was such that no definitive legal conclusion came about. In addition, there were questions over whether cphack was even properly licensed under the GPL.

In any case, the widespread opinion among those who work with Open Source licenses is that what's been released into the world can't be subsequently withdrawn. As stated in this FreeBSD document:

No license can guarantee future software availability. Although a copyright holder can traditionally change the terms of a copyright at anytime, the presumption in the BSD community is that such an attempt simply causes the source to fork.

In other words, if the license is changed to an "unfree" license, you don't get the right to enjoy any downstream changes--whether enhancements to a software program or touchups to a photograph. But the specific work that's been released to the world can't be withdrawn.

Gordon Haff is a principal IT adviser at Illuminata and has more than 20 years of IT industry experience. He writes about what's happening with enterprise servers and data centers, "Yotta-scale" computing, and related software and device trends as part of the CNET Blog Network. Disclosure.
Recent posts from The Pervasive Data Center
VMware elevates its desktop virtualization view
Intel's James Reinders on parallelism - Part 2
Intel's James Reinders on parallelism: Part 1
Red Hat debuts virtualization management
3Leaf's modern take on NUMA
Cloud computing's dual identity
Technology takes time
I/O virtualization's competing forms
Add a Comment (Log in or register)
Alas, you're wrong
by Razzl November 14, 2007 2:04 PM PST
"the widespread opinion among those who work with Open Source licenses is that what's been released into the world can't be subsequently withdrawn."

Unfortunately, these folks don't work with copyright law or they would know more about how copyright works for images, video, and other works of art. Copyright law is a very detailed and established form of law which has been strengthened to a draconian degree by the European-centric Digital Millenium Copyright Act, which withdraws many public rights which had been enjoyed under long-standing American legal precendents. Bottom line is, if the photographer completes his paperwork for copyright and his claim is accepted, Open-source software license law doesn't stand a chance of stopping him from regaining control of his work...
Reply to this comment
A question of license
by ghaff November 14, 2007 2:30 PM PST
The question isn't really about copyright law however. No one disputes that the photographer holds and continues to hold copyright on the image. The issue is that he or she has granted a license to use the image in a certain way. He can change that license for future distribution but the argument here is that he can't change it retroactively on what's already out there. Let's say a Creative Commons photo was used in a book. Is it reasonable to think that a future change to the license on that photo could turn that book into a violation?

A CNET Conversation with Eric Schmidt

CNET's Tom Krazit and Molly Wood sit down with Google CEO Eric Schmidt to discuss the future of Android, the Chrome OS, the problem of real-time search indexing, and more.

Verizon tests sending RIAA copyright notices

The No. 2 phone company, known for its reluctance to intervene in antipiracy cases, strikes an agreement to forward copyright notices on behalf of the music industry.

advertisement

About The Pervasive Data Center

This blog takes a deep (and often skeptical) look at trends big and small in the world of enterprise servers, data centers, and "Yotta-scale" computing. This means also taking into account the myriad of software, networks, and devices that are driving change in (or being driven by) these back-end systems. Stories posted to this blog may also appear on Illuminata's site.

Gordon Haff is a principal IT adviser for Illuminata of Nashua, N.H. Before becoming an IT industry analyst, Gordon held a variety of product-marketing positions at Data General, spanning more than a decade. He's programmed for DOS, Windows, and Linux; builds his own PCs; and holds engineering degrees from MIT and Dartmouth, with an MBA from Cornell. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.

Add this feed to your online news reader

The Pervasive Data Center topics

advertisement
advertisement

Inside CNET News

Scroll Left Scroll Right