3 ms·

I've not heard of that before - is that a legal employment restriction. Not that it necessarily has to be to stop people, of course. I'm going to guess you're

I've not heard of that before - is that a legal employment restriction. Not that it necessarily has to be to stop people, of course. I'm going to guess you're in USA, is it legal to stop phone workers using the phone outside work. Seems like not allowing people to work on things directly related to their actual work (due to IPR claims by the employer) would be a thing, but no OSS at all?

astura 6y ago
https://www.joelonsoftware.com/2016/12/09/developers-side-projects/ https://www.joelonsoftware.com/2016/12/09/developers-side-pr...
user5994461 6y ago
I thought we were talking about contributions at work? I find bugs in OSS libraries from working 8 hours a day on software (including in glibc and python). My last company did have a policy that you are prohibited from participating in OSS, unless getting a bunch of approvals per project or per patch. I'm risking my job sending a PR. It's work related, it should be fixed at work. (I certainly don't want to patch things in my spare time because the company forbids me to work at work). P.S. I am in London. USA would be worse.
sethammons 6y ago
I’m a decent developer. I’ve shipped code, led projects, and worked at scale. My employer owns everything I code. I’m not supposed to, legally, even write code during an interview if I’m looking for another job as they own it. I can contribute or create open source but everything must be approved by my org first. For many, that hurdle alone is too big to justify working on open source. I got a talking to for contribution to documentation on a Go project out of Facebook without proper paperwork being done and “exposing risk to my employer.”