Open source idea closely related to product at work
<p>For a while I have had an idea for an open source project. Now, I've started building something similar at work as an internal tool (so not public). So does that mean I can not go on and do the personal open source project I had in mind at first? What are the regulations for that? I mean, obviously, I can and would never just copy paste code! But concepts and ideas can be the same in some places. </p>

<p>Can I start this open source project even though I am working on something similar at my workplace which is not open source?                   </p>

<p><strong>As a programmer, what you can do in and out of work entirely depends on your employment contract and local laws.</strong> </p>

<p>For instance in my company, we encourage everyone to contribute to open source projects, including and preferably company-sponsored open source projects and this under the company copyright during work hours.</p>

<p>If I were you, I would read my contract in detail and discuss this my employer first. I would also consider ethical concerns. </p>

<p>In most cases, reusing confidential internal information to create a open source project is likely to be in contradiction with some confidential or trade secret terms of your employment, so it is best discussed first!</p>

<p>And even if you were legally allowed to do so, say your proprietary project is a now core commercial offering of your company: would you want to compete with the hand that feeds you with your personal open source project?</p>

copyright intellectual-property open-source-software