Comments on: How to Read a License Agreement http://blog.jparkhill.com/2008/12/02/how-to-read-a-license-agreement/ Business and Legal Notes, mostly Sun, 07 Mar 2010 19:48:21 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Saul_Lieberman http://blog.jparkhill.com/2008/12/02/how-to-read-a-license-agreement/comment-page-1/#comment-5564 Saul_Lieberman Wed, 03 Dec 2008 22:43:04 +0000 http://blog.jparkhill.com/?p=312#comment-5564 If there is a lengthy definitions section up front, skip it and refer back to it as needed. It will give you the context to understand any nuances in the definitions.And you won't get burned out before you get to the heart of the agreement. If there is a lengthy definitions section up front, skip it and refer back to it as needed. It will give you the context to understand any nuances in the definitions.And you won't get burned out before you get to the heart of the agreement.

]]> By: Review contracts in sections - Jay Parkhill | Drafter's Choice http://blog.jparkhill.com/2008/12/02/how-to-read-a-license-agreement/comment-page-1/#comment-5561 Review contracts in sections - Jay Parkhill | Drafter's Choice Wed, 03 Dec 2008 15:16:17 +0000 http://blog.jparkhill.com/?p=312#comment-5561 [...] Francisco technology lawyer Jay Parkhill has posted what looks like a useful a work-in-progress checklist for reviewing license agreements in topical [...] [...] Francisco technology lawyer Jay Parkhill has posted what looks like a useful a work-in-progress checklist for reviewing license agreements in topical [...]

]]> By: Jay Parkhill http://blog.jparkhill.com/2008/12/02/how-to-read-a-license-agreement/comment-page-1/#comment-5563 Jay Parkhill Wed, 03 Dec 2008 14:57:10 +0000 http://blog.jparkhill.com/?p=312#comment-5563 It's also good to remember that open source does not mean "free for any purpose". There are plenty of enterprise open source companies that provide their software (and support) under extensive license terms.<br><br>Even GPL, the most "basic" flavor of open source, comes subject to license terms and groups like the Free Software Foundation have brought litigation to enforce terms.<br><br>Thanks for the great question. A lot of people mistake open source for "I can do whatever I want with the code" and that just isn't so. Gotchas are everywhere for the unwary. It's also good to remember that open source does not mean “free for any purpose”. There are plenty of enterprise open source companies that provide their software (and support) under extensive license terms.

Even GPL, the most “basic” flavor of open source, comes subject to license terms and groups like the Free Software Foundation have brought litigation to enforce terms.

Thanks for the great question. A lot of people mistake open source for “I can do whatever I want with the code” and that just isn't so. Gotchas are everywhere for the unwary.

]]> By: D. C. Toedt http://blog.jparkhill.com/2008/12/02/how-to-read-a-license-agreement/comment-page-1/#comment-5562 D. C. Toedt Wed, 03 Dec 2008 13:19:42 +0000 http://blog.jparkhill.com/?p=312#comment-5562 Cabalamat, if the client wants to use non-open-source software, somebody has to review the license agreement; Jay's approach is a useful one. Cabalamat, if the client wants to use non-open-source software, somebody has to review the license agreement; Jay's approach is a useful one.

]]> By: Cabalamat http://blog.jparkhill.com/2008/12/02/how-to-read-a-license-agreement/comment-page-1/#comment-5559 Cabalamat Wed, 03 Dec 2008 10:54:55 +0000 http://blog.jparkhill.com/?p=312#comment-5559 Wouldn't it be simpler just to use purely open-source software, then you know you won't be caught out be license gotchas? Wouldn't it be simpler just to use purely open-source software, then you know you won't be caught out be license gotchas?

]]>