This is the mail archive of the
ecos-maintainers@sourceware.org
mailing list for the eCos project.
Re: NAND support
- From: John Dallaway <john at dallaway dot org dot uk>
- To: Simon Kallweit <simon dot kallweit at intefo dot ch>, Ricky Zheng <ricky dot zheng at i2mlabs dot com>, Jonathan Larmour <jifl at ecoscentric dot com>
- Cc: eCos Maintainers <ecos-maintainers at ecos dot sourceware dot org>
- Date: Tue, 05 May 2009 14:55:33 +0100
- Subject: Re: NAND support
- References: <49FFE56B.2070009@intefo.ch> <49FFFFBE.4030401@dallaway.org.uk> <4A0001D4.9050309@intefo.ch> <4A001A6A.3040304@dallaway.org.uk> <4A002ABD.9050009@intefo.ch>
[ moving to the ecos-maintainers list ]
Hi Simon, Ricky and Jifl
Simon Kallweit wrote:
> John Dallaway wrote:
>
>> Note also that every individual who has made a significant contribution
>> to the UFFS code would be required to sign a copyright assignment for
>> acceptance of the code into the eCos repository. Not just the original
>> author.
>
> He is the only author so far, and applied for the FSF assignment right
> away. I'm not the guru when it comes to licenses, but I think he would
> like to have UFFS on a dual license, an eCos license and a separate LGPL
> version for the current users to continue with. Is there a problem with
> this?
Dual licensing _might_ be a problem because only the copyright holder
can decide how to license the code. If the copyright assignment to the
FSF has not already been made then I would suggest that Ricky delays
copyright assignment until we have a firm plan of action.
Ricky, could you clarify whether copyright in the UFFS sources has
already been assigned to the FSF?
Jifl, can you also advise here please? Could dual licensing of UFFS
under both LGPL and the eCos Public License be achieved with a single
source base using a single license banner?
John Dallaway