<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>It is my understanding that if you work W2 as an employee all created works by default are owned by the company. All works created as a contractor are owned by you unless stipulated in a contract. Is that correct?<br><br>----- "George D. DeMet" <demet@palantir.net> wrote:
<br>> In my experience, individual contractors are typically contracted under a "work for hire" arrangement, where anything they develop becomes the property of the person or company who hired them. That person or company then has the option to redistribute the work under the terms of the GPL or another license.<br>> <br>> As a shop, we ask to retain copyright on any module code that we develop, releasing it to our clients under the terms of the GPL. This allows us to release generalized versions of those modules and patches for existing modules back out to the community, as well as re-use some code for other projects.<br>> <br>> Our standard contract includes language that stipulates that any code that might reveal information about proprietary business processes, trade secrets, etc., remains confidential and will not be released to the community or other clients. <br>> <br>> A shared copyright, where both the contractor and the vendor have the ability to redistribute code under whatever license they want, may also be a possibility.<br>> <br>> - George<br>> <br>> On Apr 24, 2010, at 5:55 AM, George Lee wrote:<br>> <br>> > Hi,<br>> > <br>> > When folks are doing contract work developing modules, is it typical to retain copyright over code or to give copyright to the folks who are contracting out to you? Do folks have legal contract language for both scenarios?<br>> > <br>> > Peace, community, justice,<br>> > - George<br>> <br><br>-- <br>Christian Pearce<br>xforty technologies<br>888-231-9331 x1119<br>http://xforty.com<br></div></body></html>