5 ms·
That is entirely possible, but not at all a problem. If something is being done in secret, so that the employee doesn't know that the other division is working
by MereInterest 8y ago
That is entirely possible, but not at all a problem. If something is being done in secret, so that the employee doesn't know that the other division is working on it, then there are no trade secrets that would be divulged by working on something similar.
That companies require you to get approval to work on something on your own time is fundamentally absurd. If I were a carpenter, I would not need permission to make a table. If I wrote ads, I would not need permission to write a book. That we think it reasonable for open source contributions to require company approval show that there is a severe overstepping of bounds on the part of the company.
- skybrian 8y agoPeople outside a company will not believe that employees of the company keep secrets from each other, at least when it suits them to believe otherwise. So like it or not, if it looks like there're a conflict of interest (even if there isn't), people will blame it on the company. So I don't really think it's so bad that they want to know what you're working on, provided that approval is usually granted.
- MereInterest 8y agoAsking for approval, even if that approval is typically granted, still implies that they have the authority to refuse permission. The farthest that the employer's moral authority extends is to ask politely to be informed. Not to require to be informed, and certainly not to require approval.
- chii 8y agoMay be the permission should be flipped - the company has to ask the employee for approval to stop the opensource project. It would work by having the employee list their projects, and the company will, when they find a conflict or some shared interest, ask for the employee to volunteer to stop their project. The employee can refuse, but typically won't.