public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Williams, Gerald S \(Jerry\)" <gsw@agere.com>
To: <cygwin-talk@cygwin.com>
Subject: RE:  Re: Rsync over ssh (pulling from Cygwin to Linux) stalls..
Date: Wed, 16 Aug 2006 13:23:00 -0000	[thread overview]
Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F68390E@PAUMAILU03.ags.agere.com> (raw)
In-Reply-To: <ebsqa3$pcj$1@sea.gmane.org>

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.

I suspect that anyone could theoretically take public
domain code and add their copyright to it (therefore
it could be submitted to RH), but IANAL, and I won't
be the first to try it. (Not that I could if I wanted
to--my company lawyers won't sign the assignment.) Of
course, this assumes that RH's sole purpose is making
sure they can legitimately use the code--if their real
purpose is making sure nobody else can use it (except
under GPL), then this wouldn't serve their purposes.

> 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.

gsw

  reply	other threads:[~2006-08-16 13:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ebq6t1$hlt$2@sea.gmane.org>
     [not found] ` <006401c6bfc0$da40e570$a501a8c0@CAM.ARTIMI.COM>
2006-08-14 17:45   ` mwoehlke
2006-08-14 17:54     ` mwoehlke
2006-08-14 18:02       ` Dave Korn
2006-08-14 18:05     ` Dave Korn
2006-08-14 19:48       ` mwoehlke
2006-08-15  0:02         ` Dave Korn
2006-08-15 15:48           ` mwoehlke
2006-08-16 13:23             ` Williams, Gerald S (Jerry) [this message]
2006-08-16 15:16               ` Christopher Faylor
2006-08-16 15:53                 ` mwoehlke
2006-08-16 16:04                   ` Corinna Vinschen
2006-08-16 16:17                   ` Christopher Faylor
2006-08-16 16:54                     ` mwoehlke
2006-08-17 16:31                       ` Williams, Gerald S (Jerry)
2006-08-17 16:42                         ` mwoehlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C89134832705D4D85A6CD2EBF38AE0F68390E@PAUMAILU03.ags.agere.com \
    --to=gsw@agere.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).