From: brian@futuretel.com
To: Anuradha Ratnaweera <anuradha@ratnaweera.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Contributing to the kernel while being employed
Date: Wed, 30 Jul 2003 11:54:07 -0700 [thread overview]
Message-ID: <20030730185407.GA12651@top.worldcontrol.com> (raw)
In-Reply-To: <1059574407.1759.26.camel@anuradha>
On Wed, Jul 30, 2003 at 10:13:27AM -0400, Anuradha Ratnaweera wrote:
>
> Slightly off-topic, but not completely ...
>
> Before working for a commercial organization, one usually has to sign a
> contract which makes all the work done during the period of employment
> (including innovations, "hobby" coding done during "after hours")
> copyrighted by the employer. This introduces various problems when one
> wishes to do open source development, especially as a hobby.
In California, USA:
There is no such thing as a free lunch, even as an employer.
A clause of that sort it technically unenforceable.
However, due to a broken tort system, there is an indirect way for
an employer to enforce such a clause. However, this same strategy
works whether you signed such an agreement or not and whether
such a clause exists or not, thus this risk isn't directly related
to the issue.
The bottom line being that having or not having such a clause
in your contract won't change your liability (at least in California).
--
Brian Litzinger
next prev parent reply other threads:[~2003-07-30 22:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 14:13 Contributing to the kernel while being employed Anuradha Ratnaweera
2003-07-30 14:36 ` Wichert Akkerman
2003-07-30 14:38 ` Bas Mevissen
2003-07-30 14:46 ` Larry McVoy
2003-07-30 15:05 ` Alan Cox
2003-07-30 18:42 ` Jamie Lokier
2003-07-30 15:08 ` Martin J. Bligh
2003-07-30 18:54 ` brian [this message]
2003-07-31 12:58 ` Henning P. Schmiedehausen
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 14:50 Anuradha Ratnaweera
2003-07-30 14:58 ` Alan Cox
2003-07-30 15:13 ` Bas Mevissen
2003-07-30 15:05 Downing, Thomas
2003-07-30 15:11 Anuradha Ratnaweera
2003-07-30 16:31 ` Martin J. Bligh
2003-07-30 16:58 ` henrique2.gobbi
2003-07-30 17:16 ` Martin J. Bligh
2003-07-30 17:43 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030730185407.GA12651@top.worldcontrol.com \
--to=brian@futuretel.com \
--cc=anuradha@ratnaweera.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox