public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Vivek Kumar <vivek@employees.org>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Assignment query
Date: Tue, 10 Aug 2004 07:04:00 -0000	[thread overview]
Message-ID: <20040810070416.GA5870@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <20040809225448.EDB075C7A2@willers.employees.org>

On Mon, Aug 09, 2004 at 03:54:48PM -0700, Vivek Kumar wrote:
> Hi,
>
> I wrote a Flash Driver Code for the company I am working for and
> would like to release it to ecos. They seem to be open to that but
> the problem I had in this is that the company still wants to use the
> code in the proprietary system.
>
> I Was wondering if there are some standard license agreements where
> they give up the copyright for the source-code but still maintain
> non-exclusive rights for them and there distributors to use the code

The standard eCos Assignment can be found at
http://ecos.sourceware.org/assign.html

The second paragraph says:

   Upon thirty days prior written notice, eCosCentric Limited agrees to
grant me non-exclusive rights to use the Work (i.e. just my changes
and enhancements, not eCos as a whole) as I see fit; (and
eCosCentric's rights shall otherwise continue unchanged).

So what you want is not a problem. Simply invoke this clause. 

   Andrew

  reply	other threads:[~2004-08-10  7:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 22:54 Vivek Kumar
2004-08-10  7:04 ` Andrew Lunn [this message]
2004-08-26 23:03 Kumar, Vivek
2004-08-27  6:56 ` Andrew Lunn
2004-08-27 10:20   ` Alex Schuilenburg
2004-08-27 12:25   ` Jonathan Larmour
2004-08-27 16:47 Kumar, Vivek
2006-01-09 15:35 Chase, Thomas
2006-01-12 15:41 ` Jonathan Larmour
2007-06-25 13:10 Rutger Hofman
2007-07-05 13:07 ` Jonathan Larmour

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=20040810070416.GA5870@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=vivek@employees.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).