From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31082 invoked by alias); 5 May 2009 23:12:11 -0000 Received: (qmail 31073 invoked by uid 22791); 5 May 2009 23:12:11 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from milford.webbase.net.nz (HELO milford.webbase.net.nz) (119.47.118.38) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 May 2009 23:12:05 +0000 Received: (qmail 21362 invoked from network); 6 May 2009 11:12:02 +1200 Received: from 203-97-181-104.dsl.telstraclear.net (HELO ?192.168.1.101?) (203.97.181.104) by milford.webbase.net.nz with (DHE-RSA-AES256-SHA encrypted) SMTP; 6 May 2009 11:12:02 +1200 Message-ID: <4A00C7BD.7000605@i2mlabs.com> Date: Tue, 05 May 2009 23:12:00 -0000 From: Ricky Zheng User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: John Dallaway CC: Simon Kallweit , Jonathan Larmour , eCos Maintainers 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> <4A004555.1030605@dallaway.org.uk> In-Reply-To: <4A004555.1030605@dallaway.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org X-SW-Source: 2009-05/txt/msg00001.txt.bz2 John Dallaway wrote: > [ 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? > I've got reply from FSF: "Thanks for your interest in contributing to free software. The Free Software Foundation only takes assignment on code that is becoming a part of the GNU project..." So no, it hasn't been assigned to the FSF. Best regards, Ricky.