3 ms·
It is dangerous to write code and try to copyright it yourself while you are on the job. It puts the FOSS project at risk for all his code contributions possibl
by zanny 13y ago
It is dangerous to write code and try to copyright it yourself while you are on the job. It puts the FOSS project at risk for all his code contributions possibly being under copyright of the company and if they found out they would probably pull all his commits.
- chaostheory 13y agoI feel if the point is 1) to avoid boredom 2) to do something constructive 3) to learn 4) to show your value to the company That will be a minor problem, especially if someone like that just decided to do a project from scratch.
- mbreese 13y agoIf it is their time and their equipment, then it's their IP. Even if they didn't know about it. In that situation, the last thing you need is the legal department on your case. Plus, what if the project got bug? How can you base something on shaky legal grounds?
- mordae 13y agoWho cares? Just re-time commits after work hours and lie. It's better than doing nothing. Just make sure your machine is not bugged.
- chaostheory 13y agoAs I've already posted above, who cares if your main goals are to not be bored and to do something constructive at the same time.