Cirrus contribution

Cirrus contribution

[Gary Thomas]

Brian,

Thanks for posting this.  We (I for sure) will be looking
at this soon, awaiting your formal assignment to the FSF.

Thanks again
  http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

RE: Cirrus contribution

[Austin, Brian]

Thanks,

I'm sorry this took so long, I hope that your branch is not too far off
from where I made mine.

Brian

-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com] 
Sent: Friday, April 10, 2009 10:33 AM
To: Austin, Brian
Cc: eCos Maintainers
Subject: Cirrus contribution

Brian,

Thanks for posting this.  We (I for sure) will be looking
at this soon, awaiting your formal assignment to the FSF.

Thanks again
  http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

RE: Cirrus contribution

[Austin, Brian]

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

Thanks,
Brian

-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com] 
Sent: Friday, April 10, 2009 10:33 AM
To: Austin, Brian
Cc: eCos Maintainers
Subject: Cirrus contribution

Brian,

Thanks for posting this.  We (I for sure) will be looking
at this soon, awaiting your formal assignment to the FSF.

Thanks again
  http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Cirrus contribution

[Gary Thomas]

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.

> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com] 
> Sent: Friday, April 10, 2009 10:33 AM
> To: Austin, Brian
> Cc: eCos Maintainers
> Subject: Cirrus contribution
> 
> Brian,
> 
> Thanks for posting this.  We (I for sure) will be looking
> at this soon, awaiting your formal assignment to the FSF.
> 
> Thanks again
>   http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739
> 


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Cirrus contribution

[John Dallaway]

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