<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jan 25, 2008, at 10:18 AM, Kevin Amerson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Verdana; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">I've been on both sides of the fence, and you have to come to the realization that if you're hired as a contractor to build something for someone else, then they own it</span></blockquote></div><br><div>In the US, this is true only if the contract specifically states it's a "work for hire." I see some folks do enter into work-for-hire contracts, but it's not something we will do.</div><div><br class="webkit-block-placeholder"></div><div>It seems that this discussion is a bit fuzzy about what is intellectual property vs. "knowhow." An absurd case is that you learn on a job how to work with Drupal hooks, and your employer owns that knowhow and you cannot work with Drupal hooks on any other job. GPL or no GPL, that is unenforceable, isn't it?</div><div><br class="webkit-block-placeholder"></div><div>Laura</div></body></html>