3 ms·
The problem with working at a company like that is that by the time you realize you are stuck, you have no relevant practical experience anymore and it can be r
by mirkules 13y ago
The problem with working at a company like that is that by the time you realize you are stuck, you have no relevant practical experience anymore and it can be rather difficult to get hired at places that are worth working at.
- chaostheory 13y agoThis is why github exists. IANAL but I'm guessing when you don't use company resources, do it during off hours, and the open source work you do has no relevance to your company's industry; publishing that work to github should be fine.
- BWStearns 13y agoFor most sane people this is the case. But many companies' boilerplate IP clauses claim ALL of the IP generated while working at the company. The vast majority of them won't give a damn but it still exposes you legally if you are under such a clause and have a side project/contribute to opensource.
- derekp7 13y agoThere is an elegant way to get out of that. Approach your management (usually requires director-level approval), and say that you are doing some volunteer web site work for [insert charity] on the weekends, and they require a signed release that your employer OK's it. This can also fall under the "requires approval for moonlighting" clause in many employee handbooks. Then, assign all copyright to your opensource work to the FSF, which is a 501c organization.