3 ms·
I tend to agree, and I think technically I am liable to get fired. What I would like to understand is the kind of problem this could cause for the open source p
by Dansvidania 7y ago
I tend to agree, and I think technically I am liable to get fired. What I would like to understand is the kind of problem this could cause for the open source project I hypothetically contributed to this way.
Can they claim ownership of my code, request it removed, cause any kind of problem or nuisance to the maintainers?
- arethuza 7y agoI would think "yes", "yes" and "yes" to all three of those questions. You don't want to give anyone an excuse to start invoking lawyers. You could ask for explicit permission - but there is a good chance (based on my own corporate experiences) that even asking would cause a lot of grief.
- zepearl 7y agoI agree. In general the risk of enterprise code and/or informations leaking out would be high when using a single device for both. And even if you're doing everything perfectly and implement an algorithm for the external project and then anytime later you end up reusing it for some internal enterprise project you and the external project might end up having a lot of problems when trying to demonstrate the timeline (best case scenario assuming that hte external project is ok sharing its code with the company you're working for). All in all too much potential trouble, I would definitely not recommend sharing a single device.
- lnsru 7y agoThe lawyers think differently than engineers. Get yourself a lawyer and try to sort things out. Your further contribution does more damage to the open source project than good.