From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12763 invoked by alias); 16 Aug 2006 15:16:27 -0000 Received: (qmail 12755 invoked by uid 22791); 16 Aug 2006 15:16:26 -0000 X-Spam-Check-By: sourceware.org Received: from pool-71-248-179-229.bstnma.fios.verizon.net (HELO cgf.cx) (71.248.179.229) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 16 Aug 2006 15:16:23 +0000 Received: by cgf.cx (Postfix, from userid 201) id 40F5113C049; Wed, 16 Aug 2006 11:16:22 -0400 (EDT) Date: Wed, 16 Aug 2006 15:16:00 -0000 From: Christopher Faylor To: The Cygwin-Talk Maiming List Subject: Re: Re: Rsync over ssh (pulling from Cygwin to Linux) stalls.. Message-ID: <20060816151621.GF13147@trixie.casa.cgf.cx> Reply-To: cygwin-talk@cygwin.com Mail-Followup-To: The Cygwin-Talk Maiming List References: <4C89134832705D4D85A6CD2EBF38AE0F68390E@PAUMAILU03.ags.agere.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C89134832705D4D85A6CD2EBF38AE0F68390E@PAUMAILU03.ags.agere.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Cygwin-Talk Maiming List X-SW-Source: 2006-q3/txt/msg00187.txt.bz2 On Wed, Aug 16, 2006 at 09:22:52AM -0400, Williams, Gerald S (Jerry) wrote: >mwoehlke wrote: >>So... are we just disagreeing over "safe", or are you actually telling >>me that RH (and thus Cygwin) would *refuse* to incorporate public >>domain code? > >In fact that is the case, and it is a shame. > >In RH's defense, there is some legal vagueness around public domain >code (and a few strange laws that add to the confusion by trying to >accommodate shareware and such). But one would think that as a huge >proponent of open source development, RH lawyers would have figured it >out by now. What Red Hat lawyers (and I, the IANAL, for that matter) have figured out is that if someone sticks a "Public Domain" tag on a piece of software, you still have to go through due diligence to find out if the software is actually encumbered or not since anyone with a text editor can put anything they like in a file. That would mean getting a release from the person's company. So, I don't see how public domain buys you much. Oddly enough the FSF has the same requirements. >>The irony of course is that the availability of a commercial license >>makes it look like Daryl's fears are in fact very well founded. :-) > >I don't care if they want to make money, but their current policy >actually prevents code from being released into the public domain. >Even if their real motivation is not monetary, that is a consequence >that I'd rather avoid. Again, Red Hat isn't doing anything different than the FSF. Red Hat does not have any interest in the "public domain". Where Cygwin is concerned, they need to be absolutely certain that they either own the code or that the code's license is conformant with their needs. cgf