3 ms·
Here's a possible solution. Do it anyway, knowing that if your company really wants to piss you off by making an issue out of it, you can (and will) tell them t
by jeffrallen 7y ago
Here's a possible solution. Do it anyway, knowing that if your company really wants to piss you off by making an issue out of it, you can (and will) tell them to piss off and quit. No job is worth sacrificing your personal life and freedom for.
When they make a problem, and you quit, if you've got someone in the company that values your contribution enough to fight for you and find a compromise to get your OSS contributions back-approved or whatever, great. The employer will benefit from the loyalty you will feel towards the person who solved the problem ("the greatest boss evar"). If your boss can't make the problem disappear, then you quit. If you've organised your life correctly, you can afford a few months of job search, and your OSS contributions are a testament to the quality of your work.
(Not saying that I ever did this. And you should probably not cross-reference "git log" with my CV either.)
- james-mcelwain 7y agoThis might be the correct advice in many scenarios but is essentially playing with fire. A company that wants revenge could easily bankrupt you with even the smallest contractual leg to stand on. Your 200k base comp isn't going to look so sweet when you're paying a lawyer $1,500 an hour to defend you from some tech giant.
- toast0 7y agoIt's one thing if you're at risk of being fired, but you've also put the project you contributed to at risk. If those contributions are potentially your (former) employer's and they were not authorized to be shared, the project is going to have to figure out how to remove them; if the employer is particularly litigous, that could get really nasty.