From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17840 invoked by alias); 8 May 2009 12:53:09 -0000 Received: (qmail 17808 invoked by uid 22791); 8 May 2009 12:53:07 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 08 May 2009 12:53:01 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id B84723B40043; Fri, 8 May 2009 13:52:58 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLg1DgF9qYoa; Fri, 8 May 2009 13:52:56 +0100 (BST) Received: from [172.31.1.127] (jifvik.dyndns.org [85.158.45.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: jlarmour@ecoscentric.com) by mail.ecoscentric.com (Postfix) with ESMTP id 53E6F3B4003D; Fri, 8 May 2009 13:52:56 +0100 (BST) Message-ID: <4A042B26.8050808@eCosCentric.com> Date: Fri, 08 May 2009 12:53:00 -0000 From: Jonathan Larmour User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) MIME-Version: 1.0 To: John Dallaway CC: Simon Kallweit , Ricky Zheng , 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/msg00002.txt.bz2 John Dallaway wrote: > Simon Kallweit wrote: >>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? Both these licences are acceptable to the FSF, so I can't see any issue with it. There's then the matter of how to achieve this. Here's my recommendation of how to modify the banner: // ####UFFSCOPYRIGHTBEGIN#### // ------------------------------------------- // This file is part of UFFS, the Ultra-low-cost Flash File System. // Copyright (C) 200x, 200y Free Software Foundation, Inc. // // UFFS is free software; you can redistribute it and/or modify it under // the terms of either: // a) the GNU General Public License as published by the Free Software // Foundation, either version 2 or (at your option) any later // version; or // b) the GNU Library General Public License as published by the Free // Software Foundation; either version 2 of the License, or (at your // option) any later version. // // UFFS is distributed in the hope that it will be useful, but WITHOUT // ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or // FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License // or GNU Library General Public License, as applicable, for more details. // // You should have received a copy of the GNU General Public License // and GNU Library General Public License along with UFFS; if not, write // to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, // Boston, MA 02110-1301, USA. // // If using UFFS under license option (a), then the following special // exception applies: // As a special exception, if other files instantiate templates or use // macros or inline functions from this file, or you compile this file // and link it with other works to produce a work based on this file, // this file does not by itself cause the resulting work to be covered // by the GNU General Public License. However the source code for this // file must still be made available in accordance with section (3) of // the GNU General Public License v2. // // This exception does not invalidate any other reasons why a work based // on this file might be covered by the GNU General Public License. // ------------------------------------------- // ####UFFSCOPYRIGHTEND#### NB, notice the indentation I have applied to the exception text, and the altered copyright banner markers. You should also add COPYING.LIB for LGPL v2 to the top of the UFFS package. I haven't been following things, but there may be a source of naming confusion with another UFFS (Unified FFS). Something to think about. Jifl -- eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. ------["The best things in life aren't things."]------ Opinions==mine