public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anuradha Ratnaweera <anuradha@ratnaweera.net>
To: Wichert Akkerman <wichert@wiggy.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Contributing to the kernel while being employed
Date: Wed, 30 Jul 2003 11:11:24 -0400	[thread overview]
Message-ID: <1059577884.1759.44.camel@anuradha> (raw)

On Wed, 2003-07-30 at 20:36, Wichert Akkerman wrote:
> Previously Anuradha Ratnaweera wrote:
> > 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.
> 
> If you signed a contract which said that you might be out of luck,
> depending on you local law. If your law allows a company to demand
> ownership of everything you do in your own time without using company
> resources than you can't work on open source projects unless your
> employer allows you to. Personally, I would never sign any contract with
> a clause like that.

What if the employer _is_ interested in contributing to the open source
under company copyright and doesn't mind using company resources, but
the employee prefers to keep copyright to himself.  The only way he can
do it is by using his own resources and time (off hours).  But this is
not possible if there is a contract that coveres the full employment
period, including after hours.

The reason why I wanted to bring up this matter was to figure out the
possibility of doing open source work purely as hobby.  One can't use
his company name for _that_.  When the company name is used, it is no
longer a hobby. ;-)

	Anuradha



             reply	other threads:[~2003-07-30 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 15:11 Anuradha Ratnaweera [this message]
2003-07-30 16:31 ` Contributing to the kernel while being employed 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
  -- strict thread matches above, loose matches on Subject: below --
2003-07-30 15:05 Downing, Thomas
2003-07-30 14:50 Anuradha Ratnaweera
2003-07-30 14:58 ` Alan Cox
2003-07-30 15:13 ` Bas Mevissen
2003-07-30 14:13 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
2003-07-31 12:58 ` Henning P. Schmiedehausen

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=1059577884.1759.44.camel@anuradha \
    --to=anuradha@ratnaweera.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wichert@wiggy.net \
    /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