From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21433 invoked by alias); 28 Mar 2011 14:40:05 -0000 Received: (qmail 21300 invoked by uid 22791); 28 Mar 2011 14:40:03 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from lo.gmane.org (HELO lo.gmane.org) (80.91.229.12) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 Mar 2011 14:39:57 +0000 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Q4Dbm-0007eF-DR for ecos-discuss@sources.redhat.com; Mon, 28 Mar 2011 16:39:54 +0200 Received: from dsl.comtrol.com ([64.122.56.22]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 28 Mar 2011 16:39:54 +0200 Received: from grant.b.edwards by dsl.comtrol.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 28 Mar 2011 16:39:54 +0200 To: ecos-discuss@sources.redhat.com From: Grant Edwards Date: Tue, 29 Mar 2011 12:56:00 -0000 Message-ID: References: <4D9074DD.70302@ecoscentric.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: slrn/pre0.9.9-102 (Linux) 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: [ECOS] Re: HOWTO: eCos on QEMU PC emulator X-SW-Source: 2011-03/txt/msg00166.txt.bz2 On 2011-03-28, Alex Schuilenburg wrote: > On 2011-03-25 15:26, John Dallaway wrote: >> Drasko >> >> Drasko DRASKOVIC wrote: >> >>>>> Second, if you re-distribute it, can not you do it the way you like - >>>>> for example putting it in git repository. >>>> Yes, you certainly can. >>> So why then the authors must assign copyright to the FSF and >>> contribute it in the order for us to put eCos sources in git tree ? >> You can put eCos-licensed sources in your _own_ repository and >> redistribute them without issue. However, it is eCos project policy that >> copyright in all contributions to the official eCos project repository >> must be assigned to the FSF. [ There are a few exceptions. ] > > The only benefit I can think of wanting to publish your own repository > would be for the rapid-turnaround in shared development of your port. > > While you can redistribute freely, there are a few good reasons why you > should consider contributing after the work is completed rather than > continuing to publish the code in your own repository. In this case, he can't consider contributing after the work is completed. He didn't write the port in question. AFAICT he was asking about creating a repository which which contained code which somebody else developed and for which a copyright assignment to the FSF hadn't been executed -- but for which the license terms allows him to redistribute the source code. In any case it's pretty much a moot point, since the author of the port has expressed a desire to contribute it. -- Grant Edwards grant.b.edwards Yow! I'm young ... I'm at HEALTHY ... I can HIKE gmail.com THRU CAPT GROGAN'S LUMBAR REGIONS! -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss