This is the mail archive of the ecos-maintainers@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Cirrus contribution

From: John Dallaway <john at dallaway dot org dot uk>
To: "Austin, Brian" <Brian dot Austin at cirrus dot com>
Cc: eCos Maintainers <ecos-maintainers at ecos dot sourceware dot org>
Date: Thu, 16 Apr 2009 17:09:45 +0100
Subject: Re: Cirrus contribution
References: <49DF669E.6030205@mlbassoc.com> <C171323BB93CB94897E300CBB6D4537F17D805A2@CLMSG-01.ad.cirrus.com> <49E74644.9050302@mlbassoc.com>

Hi Austin

Gary Thomas wrote:

> Austin, Brian wrote:
> 
>> I need some more info on why Cirrus has to sign over the "rights" to the
>> code. This is a stickler for our legal, and they are concerned as to why
>> we have to sign something.  I know, I know, but if there is any
>> documentation as to why we have to do this, it would help me a great
>> deal.  I'm still working with our legal department, and I think I can
>> get it done, but would like more ammo is yall have anything else for me
>> to help the cause.....
> 
> Look at the FSF documents/website.  The FSF is the copyright holder
> for all of eCos.  Anything which is to be added or significantly changed
> must relinquish all copyright claims to the FSF.

For an example of why the protection afforded by copyright assignment is
required, please refer to:

   http://ecos.sourceware.org/fom/ecos?file=47

John Dallaway

References:
- Cirrus contribution
  - From: Gary Thomas
- RE: Cirrus contribution
  - From: Austin, Brian
- Re: Cirrus contribution
  - From: Gary Thomas

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]