3 ms·
> Many/most developers are prohibited from working on open source projects by their employers. This is 100% untrue. IP assignment is not enforceable if you do
by pc86 7y ago
> Many/most developers are prohibited from working on open source projects by their employers.
This is 100% untrue. IP assignment is not enforceable if you do work on your own time and use your own equipment (including connectivity).
If you don't own a personal computer and your GitHub page is loaded with commits during your working hours, yeah you're going to have a hard time arguing it's not company IP. But for the vast majority of developers this is a complete non-issue, and insinuating the contrary is just FUD.
- perl4ever 7y ago"Many/most" is ambiguous. "Many" is 100% true, and having a different experience isn't any kind of a challenge to that. Even if there's some question as to the theoretical legal enforceability of an agreement, if you have to sign it to have a job, then it's not practical to challenge it. You'd have to have the resources for litigation as well as to make a living after being blacklisted. It is true that people ignore their agreements (about IP, not to run a side business, etc) when they think the company will never notice. That's still a meaningful risk that exists that some day they will.
- nullc 7y agohttps://law.justia.com/codes/california/2011/lab/division-3/2870-2872/2870 https://law.justia.com/codes/california/2011/lab/division-3/...
- vonmoltke 7y agoThis thread started with "In any state besides California and Illinois", so California state code is irrelevant. Also, posting bare links as replies is annoying. Please add some context.