public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Motoya Kurotsu <kurotsu@allied-telesis.co.jp>
Cc: Andrew Lunn <andrew.lunn@ascom.ch>, ecos-maintainers@sources.redhat.com
Subject: Re: Assignment
Date: Wed, 06 Aug 2003 13:34:00 -0000	[thread overview]
Message-ID: <3F3103CB.8090703@eCosCentric.com> (raw)
In-Reply-To: <20030806125327.A20035@white.office1>

Motoya Kurotsu wrote:
>>We have reached the stage that you need to get an assignment statement
>>signed. Please could you goto 
>>
>>http://sources.redhat.com/ecos/assign.html
>>
> 
> 
> Hi eCos maintainers;
> 
> I'm reading 'eCos Copyright Assignment Form' carefully now.
> I would like to ask some questions.

Andrew may call me an "expert" however I'm not, most importantly because I 
Am Not A Lawyer. Therefore what I say should not be read as legal advice 
in any way....

> 1) Can I or our company renounce this agreement in the future?
>    Assume the case where our company will make the intellectual 
>    policy more tight or the case where my successor doesn't accept 
>    this agreement. You may simply say "Don't send patches any more".
>    But you see legal department people often require more minuteness.

Obviously you cannot change the status of anything already contributed. 
However my understanding is that any contract can be cancelled once the 
other party (here, Red Hat) is notified, and in normal contract law either 
there would be some term explicitly covering cancellation in the contract, 
which there isn't here; or, the other party can claim damages. *But* there 
are no damages to claim!

As such, the effect is that, yes you can cancel the agreement in the 
future, once you let Red Hat know.


> 2) There is the clause titled "Which files have you changed so far,..."
>    Does it mean that the effective range of this agreement is limited
>    to the files which I would list there. Or does this agreement cover
>    all files under the ecos tree. In other words and strictly speaking, 
>    do I need to update this agreement everytime I want to change another 
>    file?

It means that we have to know what has been written so far so that 
copyright is explicitly assigned for those. Then the assignment contract 
will hold for new files in the future. There's a different legal status 
for files already written. So no, you don't need to update the agreement.

> 3) In recent source files, not RedHat but personal name is listed as
>    a copyright holder. Why? Redhat still holds copyright? Otherwise
>    the effectiveness of this agreement is in question, isn't it?
>    Or is there any legal agreement between the listed persons and RedHat?
> 
> I don't intend to be a nag but legal issues make me and our management 
> more conservative.

Sure. If it would make things easier, we are about to switch assignments 
to the Free Software Foundation. Perhaps you would prefer to assign to 
them? You can see a sneak peek at 
http://ecos.sourceware.org/ecos/maintainers/assign-fsf.html but do not 
fill it in yet as we haven't yet formally agreed on it.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

      parent reply	other threads:[~2003-08-06 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04  9:39 Assignment Andrew Lunn
2003-08-06  3:53 ` Assignment Motoya Kurotsu
2003-08-06  7:20   ` Assignment Andrew Lunn
2003-08-06 13:34   ` Jonathan Larmour [this message]

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=3F3103CB.8090703@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=kurotsu@allied-telesis.co.jp \
    /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).