If you're an open-source developer, OSCON is the closest you'll come to Mecca, whatever your religious persuasion. But OSCON has been branching out in the past few years, and this year, for the first time, it includes a a one-day, free seminar focusing on significant legal issues, called "Understanding Legal Issues in Open Source."
The seminar isn't part of the official OSCON proceedings, but is free and open to all, and is right next door at the San Jose Marriott (room Willow Glen 1)on Wednesday, July 22, and is being organized by OSCON chair Allison Randal along with Mark Radcliffe of DLA Piper and the Open Source Initiative.
The sessions include pertinent topics like "Understanding Venture Capital Investments in Open Source Projects," "Choosing a License: Ensuring that Your Intellectual Property Strategy Matches Your Goals," "Basic Legal Issues for Open Source Projects," and "Demystifying GPL Enforcement: Using the Law To Uphold Copyleft."
Speakers include Vicky Lee, DLA Piper; Josh Stein, Draper Fisher & Jurvetson; Mark Gorenberg, Hummer Winblad; Vivek Mehra, August Capital; Larry Rosen, Rosenlaw & Einschlag; Bradley Kuhn, President, Software Freedom Conservancy; Aaron Williamson, Software Freedom Law Center; and Larry Augustin, CEO, SugarCRM.
In my experience negotiating contracts to license open-source software, it's clear to me that more education like this is needed for developers, lawyers, business executives, and others in the wider open-source community. If you're anywhere near San Jose on Wednesday, you really should consider attending this one-day legal seminar.
Update below with White & Case's response. Spoiler: they weren't happy with my interpretation of their e-mail.
White & Case, a leading international law firm, has been struggling in the face of the recession, laying off 70 associates in late 2008.
Perhaps nothing makes its struggle as clear as its attempt to drum up business by scaring prospective and current clientele into retaining its services to address the very scary open-source legal threat, as a recent e-mail sent out to a friend suggests:
From: "Rieck, Christopher"
Date: April 13, 2009 8:09:09 AM PDT
To: xxxxx
Subject: Open Source Decision - New Legal Penalties on Developers?Hi Dave,
Open-source licensing--the innovative (if controversial) tool that makes source code available to the general public on certain conditions--is a growing movement most closely associated with Linux and other major software products.
The movement may well have been given a great boost by a recent court decision that makes it easier to enforce open-source licenses. But the unintended side effect may be that many software developers who incorporate bits and pieces of open-source code in commercial programs will now face greater risks of significant legal penalties for doing so.
Last December, a decision by the U.S. Court of Appeals for the Federal Circuit in the matter of Jacobsen v. Katzer held that breach of an open-source license can support a claim for copyright infringement--with associated remedies. The Court's ruling may also require recognizing that the open-source copyright owner has standing to sue downstream licensees for copyright infringement....
"Following this decision, commercial software developers should be even more cautious of incorporating any open-source code in their offerings. Potentially far greater monetary remedies (not to mention continued availability of equitable relief) make this vehicle one train to board with caution."
This is an interesting perspective, one that explicitly cuts against the generally positive perspective on the lawsuit that Mark Radcliffe and other experts on open-source law have suggested.
Indeed, legal expert Larry Lessig calls the Jacobsen decision "huge and important," and explains the appellate court's finding in very different terms than White & Case:
In nontechnical terms, the court has held that free licenses such as the (Creative Commons) licenses set conditions (rather than covenants) on the use of copyrighted work. When you violate the condition, the license disappears, meaning you're simply a copyright infringer.
This is the theory of the (GNU General Public License) and all (Creative Commons) licenses. Put precisely, whether or not they are also contracts, they are copyright licenses which expire if you fail to abide by the terms of the license.
Does that sound dire? I don't think so, either.
No, it simply means that White & Case's clients can't pilfer from the open-source community without contributing back. Since when is this something to fear?
So while it may be good business for White & Case to spread FUD (fear, uncertainty, and doubt) within its clientele to drum up business in a weak economy, the case it references is a big win for clarity around open-source licensing. This is something to celebrate, not fear.
It's also a reason to retain a different law firm, one that recognizes the opportunities in open source and isn't fixated on risks mostly of its own invention.
UPDATE: Jonathan Moskin, a partner at White & Case, responded to this post with the following:
As we explained in our e-mail to CNET, this decision may have given the open-source movement a great boost by making it easier to enforce open-source licenses. The purpose of our e-mail was to spark meaningful discussion with CNET and other publications on the issues in the decision, of which Mr. Asay was most certainly aware and which would have been clear to your readers, had the e-mail not been selectively edited to remove the invitation at the note's end.
For those who are interested, I actually could quote the e-mail in its entirety, and it would only augment my argument. I apologize to Mr. Moskin, if I misrepresented the intent of his e-mail: I was taking the words at their face value, and as an open-source advocate, I don't appreciate that value very much.
It is absolutely the case that there are legal risks in open source, but the same is 100 percent true of proprietary software. Indeed, the same risks that Mr. Moskin points out in open-source software exist in proprietary software.
Regardless, I apologize if I misread his e-mail. I'm also sorry if I seemed callous to those at his firm who lost their jobs. Unemployment is a terrible thing. I wasn't in any way trying to minimize it and apologize if it seemed that I did so.
Follow me on Twitter @mjasay.
(Credit:
DLA Piper)
This is why I think so highly of Mark Radcliffe. He just sent me his title/abstract for the upcoming Open Source Business Conference (OSBC) (March 25-26 in San Francisco), and it reveals an attorney who understands the force the law can play in advancing business strategy, not restraining it.
Implementing Your Open Source Business Strategy through Your Legal Strategy
Open source companies are adopting a variety of business strategies from dual licensing to hybrid proprietary/open source distributions and need to ensure that their legal strategy is aligned with their business strategy. This presentation will discuss the elements of a legal strategy and how they can be most effectively coordinated with the company's business strategy. It will also discuss mistakes that company's have made and how to avoid them.
I can't wait for the session. Far too many open-source companies misunderstand open source. They fail to tap into the disruptive power that open source can provide, which generally requires that they use licensing as a weapon rather than treat it as an afterthought.
A must attend session at the industry's top open-source conference.
Ashlee Vance over at The Register has a nice profile of Mark Radcliffe, partner at DLA Piper and one of the top legal minds in open source, if not the top legal mind. Mark is a friend and colleague at the Open Source Initiative, and deserves the attention.
Despite his influence over commercial open source, few know just how deeply involved he has been. The Register, however, captures his influence succinctly:
... Read moreMark Radcliffe is one of the industry's preeminent open source attorneys. He's the one I went to a few years back when I was considering starting my own open source startup. I have a huge amount of respect for him.
All of which makes his commentary on GPLv3 hearty, worthwhile reading. Mark calls out the need for an update to GPLv2 first:
The final version of the General Public License Version 3 ("GPLv3") published on June 29th is a significant improvement over General Public License Version 2 ("GPLv2") and deserves to have broad acceptance. In fairness to GPLv2, the GPLv2 was drafted in 1991: both the law relating to software and the manner in which software is developed and distributed has changed significantly since 1991.
But he doesn't end there. ... Read more
- prev
- 1
- next





