From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2674 invoked by alias); 4 Apr 2008 15:56:26 -0000 Received: (qmail 2663 invoked by uid 22791); 4 Apr 2008 15:56:26 -0000 X-Spam-Check-By: sourceware.org Received: from snape.ecoscentric.com (HELO snape.ecoscentric.com) (212.13.207.199) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 04 Apr 2008 15:55:59 +0000 Received: from localhost (snape.ecoscentric.com [127.0.0.1]) by snape.ecoscentric.com (Postfix) with ESMTP id EB2F2C54102; Fri, 4 Apr 2008 16:55:56 +0100 (BST) Received: from snape.ecoscentric.com ([127.0.0.1]) by localhost (snape.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59bhGt9JXu5O; Fri, 4 Apr 2008 16:55:55 +0100 (BST) Message-ID: <47F64F89.9080809@ecoscentric.com> Date: Fri, 04 Apr 2008 16:06:00 -0000 From: Alex Schuilenburg User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Jiri Gaisler CC: ecos-discuss@ecos.sourceware.org References: <20080403112347.68e481c9@kingfisher.sec.intern.logix-tt.com> <200804030937.m339bj00013603@mail168c2.megamailservers.com> <200804032050.20913.neundorf@kde.org> <200804032228.m33MSkCg027848@mail168c2.megamailservers.com> <20080404104457.35553e0a@kingfisher.sec.intern.logix-tt.com> <200804040912.m349CrYq028389@mail176c2.megamailservers.com> <20080404114231.7efcf59a@kingfisher.sec.intern.logix-tt.com> <47F5FC4A.2080401@gaisler.com> <20080404145330.GM7929@lunn.ch> <200804041510.m34FAdfE025938@mail175c2.megamailservers.com> In-Reply-To: <200804041510.m34FAdfE025938@mail175c2.megamailservers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Are copyright assignments detrimental to eCos? X-SW-Source: 2008-04/txt/msg00088.txt.bz2 Jiri Gaisler wrote on 2008-04-04 16:11: > > > Andrew Lunn wrote: > >>>>> I have looked at the files in eCos Pro, and majority of it has >>>>> the GPL license with the linking exception. Is there anything that >>>>> would prevent me from merging updated files from eCos Pro back >>>>> to the open CVS version? >>>> AFAICS, no, given that you legally received your copy of eCos Pro. >>> eCoscentric provides a free eCos Pro kit for the Nios processor, >>> which anyone can download. This would mean that all GPL files in >>> the kit are free to be merged with the open CVS. Or is there some >>> other catch ...? >> >> The catch is that in order for it to be included into anoncvs, the >> owner of the code has to agree and transfer the copyright to FSF. So i >> cannot just pick up eCosCentric code and commit it. eCosCentric have >> to agree to it as copyright owner. > > So if I contribute code to the anoncvs, I assign the copyright to FSF. > If eCoscentric includes the code into eCos Pro, it will still bear the > FSF copyright. If they then make a bug fix, any licensee of eCos Pro > should be able to submit the fix into anoncvs, since the copyright > is still with FSF and the code is still GPL. Have I got this right? > Or do I need to assign the copyright to eCoscentric before it is > included in the eCos Pro distribution? No. You would need to assign the code to the FSF. We (eCosCentric) are no longer accepting contributions. The FSF are now the keepers of the eCos copyright and to whom we assign any of our eCos contributions, just like the rest of the eCos community. As for submitting fixes from eCosPro to anoncvs, copyrightable fixes can only be submitted by the copyright holder, which we do from time to time. > > > What I am trying to avoid is a fork of a potential contribution, > with one version in anoncvs and some other version in eCos Pro. As Andrew says, anyone can fork the code. It is GPL code after all. The only condition is they have to adhere to the license. Anyway, forking is not in our interest, never mind the community's. We want the benefits that contributions to eCos bring, as does everyone else. eCosPro is not a fork, it is a superset of eCos. See http://www.ecoscentric.com/ecos/ecospro.shtml What you seem to be suggesting is that you want everyone else *but* eCosCentric to benefit from your potential contribution. > > Jiri. > -- Alex Schuilenburg Managing Director/CEO eCosCentric Limited Tel: +44 1223 245571 Barnwell House, Barnwell Drive Fax: +44 1223 248712 Cambridge, CB5 8UU, UK www.ecoscentric.com Reg in England and Wales, Reg No 4422071 ** Visit us at ESC Silicon Valley ** ** April 15-17 2008, Booth 3012, San Jose Convention Center ** -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss