public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Ricky Zheng <ricky.zheng@i2mlabs.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: Simon Kallweit <simon.kallweit@intefo.ch>,
	  Jonathan Larmour <jifl@ecoscentric.com>,
	 eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: NAND support
Date: Tue, 05 May 2009 23:12:00 -0000	[thread overview]
Message-ID: <4A00C7BD.7000605@i2mlabs.com> (raw)
In-Reply-To: <4A004555.1030605@dallaway.org.uk>

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.

  reply	other threads:[~2009-05-05 23:12 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 [this message]
2009-05-08 12:53           ` Jonathan Larmour
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=4A00C7BD.7000605@i2mlabs.com \
    --to=ricky.zheng@i2mlabs.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@ecoscentric.com \
    --cc=john@dallaway.org.uk \
    --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).