Most Read Latest News Blog Resources

‘Your Code Looks Like My Code‘


Policies, collective goodwill protect IP for open-source projects



November 15, 2006 — 
Businesses look to legal counsel to protect homegrown code. But for open-source projects, calling in the lawyers is rarely the first line of defense.

To address intellectual property concerns, they rely primarily on policies and procedures—spelled out in great detail—as well as the collective goodwill among members of the open-source community. “The trust level among open-source developers is high, and the tolerance of impropriety is extremely low,” said Lawrence Rosen, an attorney for technology law firm Rosenlaw & Einschlag.

According to Rosen, author of “Open Source Licensing: Software Freedom and Intellectual Property Law” (Prentice Hall 2004), being careful about the provenance of code donations to open-source projects comes down to three things: “Know the people you are working with, get it in writing and publish [the code].”

Contributors must draft a document that says: “I am giving you what I own, and I have the right to give it to you,” he explained. Once the code is published, the open-source community is quick to vet the contribution, pointing out if any part of it looks and feels like someone else’s code.

GOAL: QUICK RESOLUTION
That situation has occurred, said Cliff Schmidt, vice president of legal affairs for the Apache Software Foundation. Cases have come up where “the code is your project looks like the code in my project.” The similarity is often due to a third project, from which both parties derived pieces of the same open-source code, he said. “When that happens, there is a discussion, and we move quickly to resolve the issue.” That is typically a matter of getting the developer who contributed the code to rewrite it, so as not to infringe on a copyright, he said. “The community rallies around fixing these things as soon as possible.”

Apache requires contributors to sign a document that says their contributions are licensed to the Apache Software Foundation and its recipients, said Schmidt. They must state that they are the author of that original work, and that they or their employer owns the copyright of that work.

The Eclipse Foundation follows a similar approach. “Our focus is on ensuring that we demonstrate the provenance of the code from a copyright standpoint,” said the foundation’s executive director, Mike Milinkovich. “We work to make sure we are not accidentally shipping code we are unaware of.”

Eclipse also analyzes code contributions by running them against an automated intellectual property tool, he said. But smaller projects cannot afford to use such offerings, noted Rosen. The open-source community does a remarkable job of vetting code contributions, he said. “I have never seen a group that is so philosophically committed [to its ideals].”


Share this link: http://www.sdtimes.com/link/29798
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading



 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 3/15/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
Google Code turns 5
Google Code Turns 5, and adds a Paxos Algorithm to make the system more stable and reliable.
03/17/2010 11:16 AM EST

Test your Visual Studio 2010 know-how
Microsoft is offering free beta certification exams for Visual Studio 2010.
03/17/2010 11:08 AM EST

Microsoft lifts the hood on IE9
Microsoft is previewing IE9.
03/16/2010 01:10 PM EST

 

Events calendar tab
3/22/2010 to 3/25/2010
Santa Clara, Calif.
The Eclipse Foundation

4/12/2010 to 4/14/2010
Las Vegas
Penton Media

4/12/2010 to 4/15/2010
Santa Clara, Calif.
O'Reilly Media

4/19/2010
New York City
Flagg Management

4/25/2010 to 4/28/2010
Overland Park, Kans.
IIUG