From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: Simon Kallweit <simon.kallweit@intefo.ch>,
Ricky Zheng <ricky.zheng@i2mlabs.com>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: NAND support
Date: Fri, 08 May 2009 12:53:00 -0000 [thread overview]
Message-ID: <4A042B26.8050808@eCosCentric.com> (raw)
In-Reply-To: <4A004555.1030605@dallaway.org.uk>
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
next prev parent reply other threads:[~2009-05-08 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49FFE56B.2070009@intefo.ch>
[not found] ` <49FFFFBE.4030401@dallaway.org.uk>
[not found] ` <4A0001D4.9050309@intefo.ch>
[not found] ` <4A001A6A.3040304@dallaway.org.uk>
[not found] ` <4A002ABD.9050009@intefo.ch>
2009-05-05 13:55 ` John Dallaway
2009-05-05 23:12 ` Ricky Zheng
2009-05-08 12:53 ` Jonathan Larmour [this message]
2009-05-08 14:51 ` John Dallaway
2009-05-11 11:32 ` ricky.zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A042B26.8050808@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=ricky.zheng@i2mlabs.com \
--cc=simon.kallweit@intefo.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).