intellectual-property software open-source-software
Does publishing code under open-source license remove property rights?
<p>I have done substantial work on some software that I plan to continue to develop and improve during the course of my next employment. The contract has something to the effect of</p>

<blockquote>
  <p>All code created and developed by you prior to and during your employment shall vest and remain the property of the firm</p>
</blockquote>

<p>This is paraphrasing, but captures the essential point as I understand it, i.e. code that is relevant to the business and that is continued to be used at the firm will become property of the firm. My question is about protecting work that I have already done. <strong>Is open sourcing a software project a valid strategy to prevent a firm from acquiring sole ownership of previous works done by you</strong>. To clarify, I understand:</p>

<ul>
<li>Work done during the period I am employed by the firm will be owned by the firm</li>
<li>Extensions to a project done at the firm will be owned by the firm</li>
</ul>

<p>My main issue is related to the firm seizing <strong>sole</strong> ownership of works done prior to joining the company.</p>

<p>It is quite unusual for a company to claim ownership of work done <strong>prior to</strong> an employee's employment started. Claims on work done during the period of employment vary. It is best, from the employee's point-of-view, if the contract only claims work done "in the course of and within the scope of" the job, or possibly code developed "to be used by the company, and that are being so used". In short work done as part of the job, or on behalf of the employer, would give the employer some rights, but none in unrelated work. Your best route is to try to negotiate the agreement, to get wording such as this added to it. </p>

<p>If you can't get that, you will have to decide whether to sign such a restrictive agreement, or look for a different job with an employer with a different attitude.</p>

<p>If you do agree to such a contract, and sign it, it may well be binding on you. If so, devoting code covered by it to man open source project would not protect you -- in fact doing so might be considered in and of itself a violation of the contract, because it would mean making code agreed to be under the employer's control public.</p>

<p>The <strong>exact</strong> wording of the contract will matter, and so will the jurisdiction (country and state or province).</p>
