I got a job doing Rails development for a company three months ago, I read over the Non Disclosure pretty carefully and thought I understood it to say that the company owned the copyright to any work that I did for them, which is understandable so I signed.<p>Fast forward two and a half months and my manager tells a group of us he's trying to get management to loosen the language around intellectual property. So I go back and reread and can see that the language could be applied to anything I create anytime. I'm an entrepreneurial type person and always have side projects going, so this is a huge deal to me.<p>Today my manager clarified that we are free to contribute to open source but "Any commercial endeavor is off limits, whether designed to be monetized now or in the future."<p>Is this kind of thing common in dev world? Would/do you work under these kinds of rules?
The question of what employers usually claim can be found recently on HN - you may find the discussions either here on on the linked articles interesting:<p><a href="http://news.ycombinator.com/item?id=2208056" rel="nofollow">http://news.ycombinator.com/item?id=2208056</a><p><a href="http://news.ycombinator.com/item?id=2209181" rel="nofollow">http://news.ycombinator.com/item?id=2209181</a><p><a href="http://news.ycombinator.com/item?id=2209905" rel="nofollow">http://news.ycombinator.com/item?id=2209905</a><p>As to the question of what you "should" do, that's different, and up to you. What you "should" do is talk to your manager and say that you're not happy with outside work being verboten even when it doesn't prevent you from doing your "real job," and doesn't compete in the same space.<p>Make it clear that you understand their position, but try to get some acknowledgement of yours. You want to engage in these outside projects because you ened to keep your skills up-to-date and progressing. You don't want to be worried in case one of the side-projects takes off and makes money.<p>Start a dialog, and ask yourself how you feel about it.
I quit my last position after a former coworker got sued by my employer for creating a very popular and profitable online game. The situation put a chill over all the whole company. And eventually I decided I couldn't continue to work for them with the constant threat of being sued should I ever leave and be successful on my own.<p>Software developers really need to be educated so they are not tricked into signing legal traps like this - I wish I had been. I'm not sure why invention clauses are even legal in the first place, but all it takes to avoid a nasty situation is to read the papers before you sign and refuse to sign it.
From what I've seen, this is common, and to an extent, understandable too: a company does not want its employees to use the knowledge they gained at work in (profitable) side-projects.<p>Your best bet is to talk with the company and get a written exception, like they gave for open source.<p>Though, chances are, if both the company and your side-project is in the web development business, they won't make an exception, since the side-project can be seen as a competing product.
Ethics dictates that if the side project you are working on may be in competition with your company's products, then it would be a lot wiser to pack up and leave and pursue it. Otherwise, I don't see anything wrong with having side projects, especially if it is something you are passionate about and would add better to your bottom line.
Personally I would just ignore it. If your company owns what you do on their time and off their time that would mean you're a slave. Since slavery is almost certainly illegal where you live, I'd say you're pretty safe.<p>They might be able to give you some grief if you're doing the exact same thing at home as you're doing at work, but even then I doubt they could enforce anything. Didn't Zuckerberg sign some agreements about copying not copying work?<p>Of course, if they hear about your commercial project(s) they could fire you for it, but if they'll fire you for something like that they were probably looking for a reason anyway.