From: dshaker@qualix.com (Doug Shaker) Subject: Re: LINUX, Unix, and opportunity for change Date: 28 Dec 1992 20:40:07 GMT
in california, if you write it on your equipment during your own hours,
and using your own ideas (i.e., you don't use your employer's trade
secrets), then it is yours, no matter what your contract says.
In article 26745@netcom.com, messina@netcom.com (Tony Porczyk) writes:
>goer@ellis.uchicago.edu (Richard L. Goerwitz) writes:
>
>>mleech@bnr.ca (Marcus Leech) writes:
>>>
>>>Were it not for the fact that I have a job where everything I create is
>>> owned by my employer, I'd be as busy as Linus; contributing, rather
>>> than just pontificating. [Though it's certainly not unheard-of around
>>> here to be able to release freeware, just rather rare].
>
>>Did you actually sign a contract that gives them rights to code you cut
>>at home during off hours? If so, I'm quite amazed. Perhaps I'm just
>>naive, but this sounds like a form of slavery. I hope they pay you a
>>king's ransom.
>
>That is actually a common practice in many companies. Of course, you may
>argue that court might not uphold such broad definition. Nevertheless,
>I have seen it in contracts (and have singed at least one).
>
>t.