From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10062 invoked by alias); 3 Apr 2008 09:38:10 -0000 Received: (qmail 10046 invoked by uid 22791); 3 Apr 2008 09:38:09 -0000 X-Spam-Check-By: sourceware.org Received: from mail168c2.megamailservers.com (HELO mail168c2.megamailservers.com) (69.49.111.168) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 03 Apr 2008 09:37:50 +0000 X-Authenticated-User: jiri.gaisler.com Received: from [192.168.0.23] (c-d2c9e253.93-16-64736c12.cust.bredbandsbolaget.se [83.226.201.210]) (authenticated bits=0) by mail168c2.megamailservers.com (8.13.6.20060614/8.13.1) with ESMTP id m339bj00013603; Thu, 3 Apr 2008 05:37:46 -0400 Message-Id: <200804030937.m339bj00013603@mail168c2.megamailservers.com> Message-ID: <47F4A57F.1080501@gaisler.com> Date: Thu, 03 Apr 2008 11:14:00 -0000 From: Jiri Gaisler User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080201 SeaMonkey/1.1.8 MIME-Version: 1.0 To: Markus Schaber CC: ecos-discuss@ecos.sourceware.org References: <47F3D7DB.4000405@eCosCentric.com> <20080403112347.68e481c9@kingfisher.sec.intern.logix-tt.com> In-Reply-To: <20080403112347.68e481c9@kingfisher.sec.intern.logix-tt.com> Content-Type: text/plain; charset=UTF-8; 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/msg00039.txt.bz2 Markus Schaber wrote: > Additionally, our company has the policy that any substantial > contribution must be copy-lefted, so no-one else can make closed-source > derivates. > > Copyright assignment creates a single point of failure against > closed-source derivates, weakening the copyleft. I completely agree with Markus. We are hesitant to contribute our leon2/3 port and drivers because we do not want to have closed-source distributions (e.g. eCos Pro) using our code without contributing back fixes or improvements. The ideal solution would be to license the eCos code in LGPL. This would allow mixing proprietary applications with the kernel, while force any improvements or bug fixes to be published. Jiri. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss