From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11709 invoked by alias); 7 Apr 2008 15:22:00 -0000 Received: (qmail 11699 invoked by uid 22791); 7 Apr 2008 15:21:59 -0000 X-Spam-Check-By: sourceware.org Received: from an-out-0708.google.com (HELO an-out-0708.google.com) (209.85.132.249) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 07 Apr 2008 15:21:31 +0000 Received: by an-out-0708.google.com with SMTP id c25so347505ana.15 for ; Mon, 07 Apr 2008 08:21:29 -0700 (PDT) Received: by 10.100.240.17 with SMTP id n17mr10676765anh.49.1207581689202; Mon, 07 Apr 2008 08:21:29 -0700 (PDT) Received: by 10.100.45.10 with HTTP; Mon, 7 Apr 2008 08:21:29 -0700 (PDT) Message-ID: <18d205ed0804070821y2df3ce61w96d2992a1ad86be7@mail.gmail.com> Date: Mon, 07 Apr 2008 15:51:00 -0000 From: "Gregg Levine" To: ecos-discuss@ecos.sourceware.org In-Reply-To: <47FA2108.3090805@mlbassoc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080404114231.7efcf59a@kingfisher.sec.intern.logix-tt.com> <47F5FC4A.2080401@gaisler.com> <20080404145330.GM7929@lunn.ch> <200804041510.m34FAdfE025938@mail175c2.megamailservers.com> <47F64F89.9080809@ecoscentric.com> <200804041650.m34Goakc019397@mail175c2.megamailservers.com> <47F9FDE9.5000707@ecoscentric.com> <200804071308.m37D8Asg014776@mail168c2.megamailservers.com> <47FA2108.3090805@mlbassoc.com> 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/msg00113.txt.bz2 On Mon, Apr 7, 2008 at 9:26 AM, Gary Thomas wrote: > Jiri Gaisler wrote: > > > Alex Schuilenburg wrote: > > > > > > > Anyway, nobody is trying to force you to contribute here. I am just > trying to show you some of the benefits contributions can make to your > users, the community as well as yourself. Your changes and improvements are > yours to do with as you see fit, subject to licensing of course ;-) > > > > > > > I don't see the benefit to our users if there are two different versions > > of our contribution, one in the anoncvs and one in the Pro. In such > > case, I prefer to have our own fork where we have control over what > > goes into our code modules and where we are able to support it. > > > > The development model for kernels like RTEMS and linux seems more > > reliable to me. There is only one code base and all testing, validation > > > > At least as far as Linux goes - this is malarkey. There are more versions > of Linux out there than you could count, mostly for those platforms or > environments where the code either is not acceptable into the public > tree or simply kept back for commercial advantage. For example, you don't > see the code for the LinkSys routers in the public tree... > > > > > and bug reporting is done on the same set of code. I believe this was also > > the case for eCos as long as Cygnus maintained the code. Going back to > > this model could in fact benefit eCos Pro, since it would create a much > > larger user base for the Pro code, potentially finding more bugs and > provide > > more improvements. Just my 2 cents anyhow ... > > > > Jiri. > > > > > > > -- > ------------------------------------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------------------------------------ > > -- > > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > > Hello! Until now I've been largely an observer on this one. But regarding Gary's argument regarding the code for the LinkSys routers, there's a very good reason why it is not publicly available, and until a few years ago, not at all available. The company still refuses to believe that the GPLv2 (or GPLv3) license still applies to what they either build or make arrangements to build. And it happens that for some items they even refused to release the source code for a few portions, leaving it as an OCO (Object Code Only) binary. Which was a fact which frustrated a lot of end users of this device. By the time the firm reached its current design strategy time-period, they came close. Very close in fact. However they still have that peculiar opinion of their products and the licensing methods. And I don't know how many of you remember, but that firm only started releasing the code under what looked to be an out of court settlement on the issue. And please note that I am not a lawyer, just someone who uses the eCOS code for many ideas. (And reads one too many books taking place in a certain lawyer's time and place.) -- Gregg C Levine gregg.drwho8@gmail.com "This signature was once found posting rude messages in English in the Moscow subway." -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss