GitHub lets staff own IP developed for personal projects using company resources
Once upon a time, I was looking for a job, in straightened circumstances. I found a so-so match, and since I was in danger of missing a mortgage payment, I decided to accept their offer. Pragmatism and all that.<p>Well, I went in and picked up the documents, and told them I needed to read them before signing and returning them to the company. I looked at the IP clause, and it said the company owned anything and everything I created or invented while an employee, in any field of endeavor.<p>I called the founder to renegotiate.<p>&quot;What if,&quot; I posited, &quot;I write a blog post. The way I read this, the company owns the copyright on my blog post.&quot;<p><pre><code>  &gt; Yes.
</code></pre>
&quot;Or if I take a video of a climbing trip, the company owns that video.&quot;<p><pre><code>  &gt; We&#x27;d never exercise that right. But we reserve the right.
</code></pre>
&quot;Well, I&#x27;m not sure I want to agree that anything I create, even on my own time and property and with my own equipment, belongs to you.&quot;<p><pre><code>  &gt; Now that you mention it, I&#x27;m not sure I want to employ
  &gt; someone who uses their creative energy for anything except
  &gt; the company&#x27;s business.
</code></pre>
&quot;Thanks for the clarification!&quot;<p>My next call was to a realtor, I put my house up for sale. There was no way I wanted to be in a position where I would feel like I had no choice but to accept an offer like this.<p>I went through some hard times, but as it turned out, that blog that I did end up writing on-and-off over the years turned out to be valuable. Not directly in money, but in satisfaction. It lead to some work, but even more importantly, it led to communities like Hacker News and meeting programmers around the world.<p>If I&#x27;d agreed to that contract, there might not be a &quot;raganwald&quot; today.