Media praise for Intellectual Property and Open Source
Have a blog? Join our Reader Review Program
"Over the past 10 years, I've read every open-source legal book written. Lindberg's book is by far the best. If you've wanted a book that helps to explain complex open-source legal questions in a readable, approachable style, this is it. If you've wanted to know how to write an open-source contract, or whether patents were going to be the undoing of your project, here's your book...It truly is the best thing written about open source since Eric Raymond's "The Cathedral and the Bazaar." Yes, I really mean it. I think it's that good for helping people navigate the questions that arise from open source."
-- , The Open Road
"Clear, correct, and deep, this is a welcome addition to discussions of law and computing for anyone -- even lawyers! "
-- , founder of the Stanford Center for Internet and Society
"...As open-source software becomes mainstream, and is integrated into larger systems, these age-old arguments are less theoretical than ever, and should be understood not only by developers, but also by managers and executives of organizations working with open source. Van Lindberg's new book is an excellent place to start..."
-- , OStatic
"This is well written, clear, and very complete. Highly recommended."
-- , APLawrence.com
"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. "
-- , Duffbert's Random Musings
"No book could replace the advice of competent legal counsel, but reading Intellectual Property and Open Source from cover to cover will give the average free software developer a clear understanding of the legal terrain she will have to navigate as she creates, improves, or uses free software."
-- , Ars Technica
"There isn't a person writing code in this country who is not impacted by US intellectual property laws. I think that it is safe to say, that not all coders have a strong understanding of just what those laws are, let alone what they mean. Stepping into this gap is programmer become lawyer Van Lindberg with his new book Intellectual Property and Open Source. Lindberg has really done something special with this volume. I don't think I've ever read a tech oriented work where I've felt so convinced that I was reading something that would become a standard by which others would come to be judged."
-- , Slashdot.org
"I thoroughly enjoyed this book...I was convinced the author was someone I could relate to when in the chapter on trade secrets, he used the 'Flaming Moe' as one of his examples of trade secret calamities. "
-- , Amazon.com
"...a valuable guide for anyone in the technical world who wishes to know about legal issues of intellectual property, and particularly for anyone in, or contemplating, an open source project."
-- , Internet Review Project
"...an excellent book. Van Lindberg has done an outstanding job of navigating a dry and complex subject in an engaging and precise manner. If you're a programmer, or involved in open source projects, you need to read it--thankfully you'll enjoy it."
-- , The Voidspace Techie Blog
"So in summary, an excellent book. Van Lindberg has done an outstanding job of navigating a dry and complex subject in an engaging and precise manner. If you're a programmer, or involved in open source projects, you need to read it - thankfully you'll enjoy it."
-- , The Voidspace Techie Blog
"Most of us think we understand what Open Source means, but in fact we don't. Van Lindberg's Intellectual Property and Open Source: A Practical Guide to Protecting Code from O'Reilly attempts to remedy that. It's a valiant attempt, and if you finish the book - it's both a handbook and an attempt at explanation - you can be pretty sure you know a lot more than you did before you started. "
-- , Chaos Manor
"Recently I was faced a problem to determine which code can be used within the software when different licenses are mixed. Which was not a pleasant task. Studying legal related topics usually doesn't count into 'ten most interesting' things software engineers like to do." Full Review >
-- , www.owsiak.org