Intellectual Property and Open Source: A Practical Guide to Protecting Code (Paperback)

by Van Lindberg (Author)
Key Phrases: contract law principles, wolf spider, simple blog, United States, Flaming Moe, Artistic License (more...)

Editorial Reviews

Product Description
"Clear, correct, and deep, this is a welcome addition to discussions of law and computing for anyone -- even lawyers!" -- Lawrence Lessig, Professor of Law at Stanford Law School and founder of the Stanford Center for Internet and Society

If you work in information technology, intellectual property is central to your job -- but dealing with the complexities of the legal system can be mind-boggling. This book is for anyone who wants to understand how the legal system deals with intellectual property rights for code and other content. You'll get a clear look at intellectual property issues from a developer's point of view, including practical advice about situations you're likely to encounter.

Written by an intellectual property attorney who is also a programmer, Intellectual Property and Open Source helps you understand patents, copyrights, trademarks, trade secrets, and licenses, with special focus on the issues surrounding open source development and the GPL. This book answers questions such as:

How do open source and intellectual property work together? What are the most important intellectual property-related issues when starting a business or open source project? How should you handle copyright, licensing and other issues when accepting a patch from another developer? How can you pursue your own ideas while working for someone else? What parts of a patent should be reviewed to see if it applies to your work? When is your idea a trade secret? How can you reverse engineer a product without getting into trouble? What should you think about when choosing an open source license for your project?

Most legal sources are too scattered, too arcane, and too hard to read.Intellectual Property and Open Source is a friendly, easy-to-follow overview of the law that programmers, system administrators, graphic designers, and many others will find essential.

About the Author
Van Lindberg is a software engineer and practicing attorney. What he does most, though, is translate - from "lawyer" to "engineer" and back. He likes working with both computer code and legal code to get things done. Van's current work touches both traditional intellectual property and the emerging field of open source law, where he advises businesses and open source groups on intellectual property issues.

Product Details

• Paperback: 390 pages
• Publisher: O'Reilly Media, Inc. (July 1, 2008)
• Language: English
• ISBN-10: 0596517963
• ISBN-13: 978-0596517960
• Product Dimensions: 9.1 x 7 x 1.1 inches
• Shipping Weight: 1.3 pounds (View shipping rates and policies)
• Average Customer Review: 4.6 out of 5 stars See all reviews (14 customer reviews)
• Amazon.com Sales Rank: #269,614 in Books (See Bestsellers in Books)

  Popular in these categories: (What's this?)

  #44 in	Books > Computers & Internet > Business & Culture > Digital Law
  #77 in	Books > Nonfiction > Law > Intellectual Property > Patent, Trademark & Copyright
  #87 in	Books > Professional & Technical > Law > Intellectual Property

Customer Reviews

Most Helpful Customer Reviews

12 of 12 people found the following review helpful:

5.0 out of 5 stars The best legal book on open source I've read (and I've read them all), July 15, 2008

By	Matthew Asay (Salt Lake City, Utah) - See all my reviews (REAL NAME)

I've been involved in open source and the software world for over 10 years now, and have read every book on open source and legal issues that has been written. This is by far the best.

Why? Because it lays out in clear, easy-to-understand language what open source means for the developer. You don't have to be a legal expert to grasp the principles laid out in the book. In fact, Lindberg walks the reader through commonly obtuse principles by analogizing to software principles that the reader will easily understand.

In addition, it's very well-written. Lindberg has an outstanding style that makes this readable. I won't say it's like reading Charles Dickens, but at times it really is that enjoyable.

7 of 7 people found the following review helpful:

4.0 out of 5 stars Good Organization and Great Writing, July 17, 2008

By	James Grimmelmann (New York) - See all my reviews (REAL NAME)

I was lucky enough to see this book in draft form, and even before the final spit-and-polish touches, it was a pleasure to read. The author has a real gift for metaphor; almost every chapter is organized around a vivid, memorable concept. He compares the format of a patent document to the ELF file format; he uses the secret recipe for the Flaming Moe to talk about trade secrets. The result is an introduction to IP law that's unusually fun to read.

But the clarity and verve of the writing doesn't detract from the book's main goal: showing the reader how the IP system works and affects open source software. The author has exercised very good judgment in paring down an immensely complicated body of law into an approachable set of important principles. The reader gets the big picture overview, a clear understanding of the truly important details, and a good sense of what else is out there and how to find out more. This book doesn't try to be a definitive reference or a dumbed-down sketch. Instead, it hits the sweet spot in between: informative and readable.

5 of 5 people found the following review helpful:

5.0 out of 5 stars Targeted well for the technology professional..., September 6, 2008

By	Thomas Duff "Duffbert" (Portland, OR United States) - See all my reviews (TOP 50 REVIEWER)    (REAL NAME)

As a software developer, it's almost a certainty that you either participate in or use open source software somewhere in your computing environment. But even though you may have the source code sitting in front of you, it doesn't mean you can anything you darn well please with it. Van Lindberg's book Intellectual Property and Open Source: A Practical Guide to Protecting Code does a very good job in presenting the intricacies of open source licensing in a way that won't automatically put a developer to sleep. Granted, there's still a lot of legal concepts to wade through, but in my opinion he hit the right mix between legalities and practicalities.

Contents: The Economic and Legal Foundations of Intellectual Property; The Patent Document; The Patent System; Copyright; Trademarks; Trade Secrets; Contracts and Licenses; The Economic and Legal Foundations of Open Source Software; So I Have An Idea...; Choosing A License; Accepting Patches and Contributions; Working With The GPL; Reverse Engineering; Incorporating As A Non-Profit
Appendices: Sample Proprietary Information Agreement (PIA); Open Source License List; Free Software License List; Fedora License List and GPL Compatibility; Public Domain Declaration; The Simplified BSD License; The Apache License, Version 2.0; The Mozilla Public License, Version 1.1; The GNU Lesser General Public License, Version 2.1; The GNU Lesser General Public License, Version 3; The GNU General Public License, Version 2, June 1991; The GNU General Public License, Version 3, June 2007; The Open Software License, Version 3.0
Index

Lindberg accomplishes a couple of purposes in this book. The first few chapters trace the history and general concepts of intellectual property law, such as patents and trade secrets. This is necessary, in that it lays the groundwork to be able to understand what part of your work may or may not be covered by intellectual property laws. While there are plenty of legal concepts and examples cited, he doesn't get so far down into the weeds as to make the material irrelevant to the target audience... technology professionals. The last half of the book then uses that foundation to talk specifically about open source software, licenses, and legal issues being faced today. And really, it's more complex than you'd think (but isn't *anything* legal overly complex?) Each of the licenses he covers has certain advantages and disadvantages that can make a significant impact on how you and others can use your software going forward. For instance, one license may allow the user to use it in any way they see fit, including using it in their own non-open source software. Other licenses actually force any software project using the open source code to also be bound by the same license, meaning that your work has to be made available in open source form to others. Based on what you plan on building and how you want to market it, this could make the difference between a thriving business or a ruinous lawsuit. And again, the writing is appropriate for the technology professional, not four year law students looking to become a partner and retire by the age of 40.

For anyone involved in creating an open-source project (or what they *think* an open source project should be), this should be essential reading. And if you've ever downloaded something from Sourceforge to include in one of your own projects, you also need to read this to clearly understand your rights and obligations. I know we techies would prefer to let other people figure out the legal stuff, but it's not worth it to have your next killer application idea bankrupt you in court...