public inbox for
 help / color / mirror / Atom feed
From: Jonathan Larmour <>
To: Elaine Lee <>,
	eCos Maintainers <>
Cc: Iain Scott <>, Paul Riley <>
Subject: Re: Copyright Assignment from Altera Corp.
Date: Thu, 13 Jan 2005 23:46:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> To:,
> Cc: Iain Scott <>, Paul Riley <>
> Hello Andrew and eCos maintainers,
> I am writing regarding a contribution of computer software source code
> Altera Corporation will be making to eCos, subject to execution of a
> copyright assignment agreement between Altera and eCos.  I believe Iain
> Scott and Paul Riley of Altera has been in contact with Andrew Lunn
> about this contribution.

Andrew asked me to look at the assignment text, and I discussed with and 
passed it over to the eCosCentric CEO for comments on the legal aspects.

> The contribution relates to a port of the eCos operating system for Nios
> II, and drivers for various SOPC Builder peripherals.  I have reviewed
> your web pages regarding contributing to eCos and copyright assignments.
> Altera has a standard Assignment of Copyright for open source and
> freeware computer software, which is attached.  I believe this
> Assignment addresses the points brought up in eCos' copyright assignment
> language and description.

There are a few subtle differences that mean we can't use the exact text as 
you supplied straight off I'm afraid.

1) First of all the definition of "Works" and separately clause 7 refer to 
code checked into the Assignee's source code repository by Altera. That 
isn't the way it works with eCos (especially since the Assignee doesn't 
manage the relevant repository!). Something along the lines of "posted on 
the mailing list or via the eCos bugzilla 
web site" would be more appropriate.

2) Secondly, the normal eCos license consists of the GNU General Public 
License (GPL), but also an exception to some of the terms of the GPL (cf. 
<>). Clause 4 has problems 
with the exception part which is written to intentionally permit derived 
works where the only source code that must be given out is that of eCos 
itself, and not the application to which it is linked (despite the whole 
being a derived work).

As such we think the best solution is for clause 4 to be amended so that 
the mentions of the "the work" from the 4th, 5th, and 7th lines of clause 4 
  would become "the Works".

3) Similarly for clause 5: 'any program "based on the Works"' should 
instead be replaced by 'the Program "based on the Works"'

With those changes, the assignment would suit our needs and be compatible 
with the eCos license.

However if you find it easier to just go with the normal assignment at 
<>, then that's fine too.

Hope this helps and thanks for contributing back!

(eCos Maintainer)
eCosCentric    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

       reply	other threads:[~2005-01-13 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2005-01-13 23:46 ` Jonathan Larmour [this message]
2005-01-19 16:53 Elaine Lee

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).