Skip to main content Accessibility help
×
Hostname: page-component-7479d7b7d-qs9v7 Total loading time: 0 Render date: 2024-07-11T12:58:15.026Z Has data issue: false hasContentIssue false

6 - Legal Issues in Open Source

Published online by Cambridge University Press:  16 January 2010

Fadi P. Deek
Affiliation:
New Jersey Institute of Technology
James A. M. McHugh
Affiliation:
New Jersey Institute of Technology
Get access

Summary

Much of the impetus for the free and open software movement arose as a reaction to legal issues related to software licensing. Consequently, questions concerning what is commonly called intellectual property have been a habitual feature of the open source landscape. Intellectual property includes creations like copyrighted works, patented inventions, and proprietary software. The purpose of this chapter is to survey some of the relevant legal issues in this domain in an accessible manner informative for understanding their relevance to free and open development. The legal and business mechanisms that have been developed to protect intellectual property are intended to address the core objective of protecting creations in order to provide appropriate incentives for innovators. Traditionally, such protection has been accomplished through exclusion. For example, under copyright law, one is not allowed to distribute a copyrighted work without the authorization of the owner of the copyright. The General Public License (GPL) that lies at the heart of the free software movement takes an unconventional perspective on the use of copyright. It focuses not on how to exclude others from using your work, but on how to preserve the free and open distribution of your work when you do allow others to modify and redistribute it (Weber, 2004). We will consider the basic legal concepts associated with intellectual property and how they have been brought to bear in the open source movement.

Type
Chapter
Information
Open Source
Technology and Policy
, pp. 222 - 264
Publisher: Cambridge University Press
Print publication year: 2007

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

References

Andersen, T. (2004). Behlendorf on Open Source. http://www.itwriting.com/ behlendorf1.php. Accessed December 1, 2006.
Anderson, R. (2003a). ‘Trusted Computing’ Frequently Asked Questions, Version 1.1. http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html. Accessed December 1, 2006.Google Scholar
Anderson, R. (2003b). ‘Trusted Computing’ and Competition Policy – Issues for Computing Professionals. Upgrade. The European Journal for the Informatics Professional, 4(3), 35–41.Google Scholar
Asay, M. (2003). Open Source's General Public License: Why Microsoft Is So Scared. Wasatch Digital IQ, 3(1). http://www.wasatchdigitaliq.com/parser.php?nav=article&article_id=49. Accessed December 1, 2006.Google Scholar
Bessen, J. (2002). What Good is Free Software? In: Government Policy toward Open Source Software, Hahn, R. W. (editor). Brookings Institution Press, Washington, DC.Google Scholar
Capek, C., Frank, S., Gerdt, S., and Shields, D. (2005). A History of IBM's Open-Source Involvement and Strategy. IBM Systems Journal, 44(2), 249–257.Google Scholar
Carver, B. (2005). Share and Share Alike: Understanding and Enforcing Open Source and Free Software Licenses. Berkeley Technology Law Journal, 20, 443–481.Google Scholar
Corbet, J. (2003). Binary Modules and Derived Works. http://lwn.net/Articles/61490/. Accessed December 1, 2006.
Downen, M. (2005). Obfuscation. Posted May 26. http://blogs.msdn.com/CLRSecurity/. Accessed December 1, 2006.
Epplin, J. (2001). Using GPL Software in Embedded Applications: Wind River's Worries. http://www.linuxdevices.com/articles/AT9161119242.html. Accessed December 1, 2006.
Engelfriet, A. (2005). Patent Risks of Open Source Software. http://www.iusmentis.com/computerprograms/opensourcesoftware/patentrisks/. Accessed December 1, 2006.
Evans, D. (2002). Politics and Programming: Government Preferences for Promoting Open Source Software. In: Government Policy toward Open Source Software, Hahn, R. W. (editor). Brookings Institution Press, Washington, DC.Google Scholar
Feller, J. and Fitzgerald, B. (2002). Understanding Open Source Software Development. Addison-Wesley, Pearson Education Ltd., London.Google Scholar
Fishman, S. (2004a). Open Source Licenses Are Not All the Same. 11/18/2004. http://www.onlamp.com/pub/a/onlamp/2004/11/18/licenses.html. Accessed December 1, 2006.
Fishman, S. (2004b). Web and Software Development: A Legal Guide. Nolo Pub., Berkeley, CA.Google Scholar
Fitzgerald, B. and Bassett, G. (2003). Legal Issues Relating to Free and Open Software. In: Essays in Technology Policy and Law, vol. 1. Fitzgerald, B. and Bassett, G. (editors). Queensland University of Technology, School of Law, Brisbane, Australia, Chapter 2.Google Scholar
Hollaar, L. (2002). Legal Protection of Digital Information. BNA Books. http://digital-law-online.info/. Accessed January 20, 2007.Google Scholar
IBM Press Release. (2005). IBM Pledges 500 U.S. Patents to Open Source in Support of Innovation and Open Standards. January 11. Armonk, New York.
Jassin, L. and Schecter, S. (1997). Copyright Permission and Libel Handbook: A Step-by-Step Guide for Writers, Editors and Publishers. John Wiley & Sons, New York.Google Scholar
Jones, P. (2003). The GPL Is a License, Not a Contract, Which Is Why the Sky Isn't Falling. December 14. http://www.groklaw.net/article.php?story=20031214210634851. Accessed December 20, 2006.
Jones, P. (2005). Software, Reverse Engineering, and the Law. http://lwn.net/Articles/134642/. Accessed December 1, 2006.
Knuth, D. (1990). The Future of TEX and METFONT., Nederlandstalige TeX Gebruikersgroep, MAPS 5, 145–146. www.ntg.nl/maps/maps5.html. Accessed January 5, 2007.Google Scholar
Landau, M. (2000) “Statutory Damages” in Copyright Law and the MP3.com Case. http://chnm.gmu.edu/digitalhistory/links/pdf/chapter7/7.24b.pdf. Accessed December 1, 2006.
Lerner, J. and Tirole, J. (2005). The Scope of Open Source Licensing. Journal of Law, Economics, and Organization, 21(1), 21–56.Google Scholar
Magid, L. (2005). It Pays to Read License Agreements. http://www.pcpitstop.com/spycheck/eula.asp. Accessed December 1, 2006.
McMillan, R. (2002). Patent War Pending? Lawrence Rosen on How Open Source Can Protect Itself from Software Patents. http://linuxplanet.com/linuxplanet/interviews/4575/1/. Accessed December 1, 2006.
Meeker, H. (2006). Only in America? Copyright Law Key to Global Free Software Model. LinuxInsider. May 16.Google Scholar
Microsoft. (2006). Microsoft and Novell Announce Broad Collaboration on Windows and Linux Interoperability and Support. Microsoft Press Release. November 2. http://www.microsoft.com/presspass/press/2006/nov06/11 02MSNovellPR.mspx. Accessed January 20, 2007.
Moglen, E. (1999). Anarchism Triumphant: Free Software and the Death of Copyright. First Monday, 4(8). http://www.firstmonday.org/issues/issue4_8/moglen/index.html. Accessed January 5, 2007.Google Scholar
Moglen, E. (2001). Enforcing the GNU GPL. http://www.gnu.org/philosophy/enforcing-gpl.html. Accessed December 20, 2006.
Moglen, E. (2003). Professor Eben Moglen Replies. February 20. http://interviews.slashdot.org/interviews/03/02/20/1544245.shtml. Accessed February 18, 2007.
Open Source Risk Management. (2004). Results of First-Ever Linux Patent Review Announced, Patent Insurance Offered by Open Source Risk Management. August 2. http://www.osriskmanagement.com/press_releases/press_release_080204.pdf. Accessed December 20, 2006.
OSS Watch (2006). The GNU General Public License – An Overview. Open Source Advisory Service. http://www.oss-watch.ac.uk/resources/gpl.xml. Accessed December 1, 2006.
Payne, C. (2002). On the Security of Open Source Software. Information Systems Journal, 12(1), 61–78.Google Scholar
Perens, B. (1999a). It's Time to Talk about Free Software Again. http://lists.debian.org/debian-devel/1999/02/msg01641.html. Accessed January 5, 2007.
Perens, B. (1999b). The Open Source Definition. In: Open Sources: Voices from the Open Source Revolution, Stone, M., Ockman, S., and DiBona, C. (editors). O'Reilly Media, Sebastopol, CA, 171–188.Google Scholar
Perens, B. (2004). The Problem of Software Patents in Standards. http://perens.com/Articles/PatentFarming.html. Accessed December 1, 2006.
Perens, B. (2006). The Monster Arrives: Software Patent Lawsuits against Open Source Developers. June 30. http://technocrat.net/d/2006/6/30/5032. Accessed January 5, 2007.
Peters, D. (2006). Software Patents and Open Source Software: An Overview of Patent Provisions in the First Draft of GPLv3. American Intellectual Property Law Association 2006 Spring Meeting, May 3–5, Chicago.Google Scholar
Raymond, E. (2001). Email from Raymond to Torvalds. Subject: Controversy over Dynamic Linking – How to End the Panic. June 21, 2001, 14:14:42. Linux Kernel Mailing List Archive. http://lwn.net/2001/0628/a/esr-modules.php3. Accessed February 18, 2007.Google Scholar
Rosen, L. (2001a). Naming Your Open Source Software. http://www.rosenlaw.com/lj6.htm. Accessed December 1, 2006.
Rosen, L. (2001b). The Unreasonable Fear of Infection. RosenLaw.com, 32. September 23, 2001. http://www.rosenlaw.com/html/GPL.PDF. Accessed December 1, 2006.
Rosen, L. (2002). Why the Public Domain Isn't a License. Tuesday, 2002–10–01, 01:00. Linux Journal. http://www.linuxjournal.com/article/6225. Accessed December 19, 2006.Google Scholar
Rosen, L. (2003). Derivative Works. http://www.linuxjournal.com/article/6366. Accessed December 1, 2006.
Rosen, L. (2005). Open Source Licensing: Software Freedom and Intellectual Property Law. Prentice Hall, Upper Saddle River, NJ.Google Scholar
Rosenberg, D. K. (2005). Open Source Licensing: Software Freedom and Intellectual Property Law: Book Review. Open Source Licensing Page, Stromian Technologies.Google Scholar
Samuels, E. (1993). The Public Domain in Copyright Law. Communications Media Center at New York Law School. Journal of the Copyright Society of the USA, 41, 137–182. http://www.edwardsamuels.com/copyright/beyond/articles/public.html. Accessed December 6, 2006.Google Scholar
Samuelson, P. (2002). Reverse Engineering under Siege. Communications of the ACM, 45(10), 15–20.Google Scholar
Schwartz, M. (2001). Reverse-Engineering. http://www.computerworld.com/softwaretopics/software/appdev/story/0,10801,65532,00.html. Accessed December 1, 2006.
Shapiro, C. (2001). Navigating the Patent Thicket: Cross Licenses, Patent Pools and Standard Setting. In: Innovation Policy and the Economy, Jaffe, A., Lerner, J., and Stern, S. (editors). National Bureau of Economics. http://faculty.haas.vberkeley.edu/shapiro/thicket.pdf. Accessed December 1, 2006.Google Scholar
Stallman, R. (1996/2001). Categories of Free and Non-Free Software. http://www.gnu.org/philosophy/categories.html. Accessed January 20, 2007.
Stallman, R. (2001). Free Software: Freedom and Cooperation. www.gnu.org/events/rms-nyu-2001-transcript.txt. Accessed December 1, 2006.
Stallman, R. (2005). Fighting Software Patents – Singly and Together. http://www.gnu.org/philosophy/fighting-software-patents. Accessed December 1, 2006.
Stone, L. (2004). The Linux Killer. Issue 12.07. http://www.wired.com/wired/archive/12.07/linux.html. Accessed December 1, 2006.
Tonella, P.Antoniol, G., Fiutem, R., and Calzolari, F. (2000). Reverse Engineering 4.7 Million Lines of Code. Software Practice and Experience, 30, 129–150.Google Scholar
Ueda, M., Uzuki, T., and Suematsu, C. (2004). A Cluster Analysis of Open Source Licenses. In: Proceedings of 1st International Conference on Open Source Systems, Genova.Google Scholar
Walli, S. (2005). Perspectives on the Shared Initiative. http://www.onlamp.com/pub/a/onlamp/2005/03/24/shared_source.html. Accessed December 1, 2006.
Warrene, B. (2005). Navigating Open Source Licensing. http://www.sitepoint.com/article/open-source-licensing. Accessed December 1, 2006.
Webbink, M. (2003). Understanding Open Source Software. New South Wales Society for Computers and Law Journal, 51. http://www.groklaw.net/article.php?story=20031231092027900. Accessed December 1, 2006.Google Scholar
Weber, S. (2004). The Success of Open Source. Harvard University Press, Cambridge, MA.Google Scholar
West, J. (2003). How Open Is Open Enough? Melding Proprietary and Open Source Platform Strategies. Research Policy, 32(7), 1259–1285.Google Scholar
Wheeler, D. (2003). Make Your Open Source GPL-Compatible. Or Else. Revised November 2006. http://www.dwheeler.com/essays/gpl-compatible.html. Accessed December 1, 2006.Google Scholar
Wilson, R. (2005). The Mozilla Public License – An Overview. Open Source Advisory Service. http://www.oss-watch.ac.uk/resources/mpl.xml. Accessed December 1, 2006.Google Scholar
Zittrain, J. (2004). Normative Principles for Evaluating Free and Proprietary Software. University of Chicago Law Review, 71(1), 265.Google Scholar

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×