public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: "Chase, Thomas" <Tom_Chase@dtccom.com>
Cc: "'ecos-maintainers@ecos.sourceware.org'"
	<ecos-maintainers@ecos.sourceware.org>
Subject: Re: Assignment query
Date: Thu, 12 Jan 2006 15:41:00 -0000	[thread overview]
Message-ID: <43C6789F.10606@jifvik.org> (raw)
In-Reply-To: <3EDBCCE80E95E744A99895CA464987C44BB087@dtcsrvr09>

Chase, Thomas wrote:
> Hi,
> 
> I am in the process of doing a copyright assignment.  I have the company
> disclaimer taken care of, and am wondering if I can use something similar to
> what I have attached to cover the individual writers.  I am trying to avoid
> sending multiple assignments to cover the work that we have done and will do
> in the future.  So instead of multiple copies of the individual assignment
> (one for each of the people that have participated in a port) can I send
> something like: 
[snip]

As long as DTC Communications _is_ the copyright holder of the works in 
question (usually due to a clause in the employee's employment contract) 
then that should be fine. Thanks.

Jifl
-- 
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

  reply	other threads:[~2006-01-12 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 15:35 Chase, Thomas
2006-01-12 15:41 ` Jonathan Larmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-25 13:10 Rutger Hofman
2007-07-05 13:07 ` Jonathan Larmour
2004-08-27 16:47 Kumar, Vivek
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-09 22:54 Vivek Kumar
2004-08-10  7:04 ` Andrew Lunn

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=43C6789F.10606@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=Tom_Chase@dtccom.com \
    --cc=ecos-maintainers@ecos.sourceware.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).