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: Handling special characters (\/:*?"<>|) gracefully
Date: Tue, 30 May 2006 14:04:00 -0000	[thread overview]
Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F3E0B33@PAUMAILU03.ags.agere.com> (raw)

Joe Smith wrote:
> If you modify it in any way, you have created a derived work.  That
> is very well established.  If your modifications are non-trivial,
> then you would hold copyright on the derived work, so there should
> be absolutly no problems releasing the dirived work under the GPL.

Cygwin core code is not simply GPL'ed. RedHat owns the copyright
and chooses to release a version under the GPL. They insist on
having clear rights to the code.

If you can prove that some code is public domain, everybody has
clear rights to it. I had hoped that publishing something as a
public domain project would be sufficient for RedHat, but it
apparently is not. They want a clear trail of accountability.

Christopher Faylor wrote:
> So, while someone did tell me that public domain software
> might be ok to include, practically speaking, we only have
> one approved mechanism for getting changes into cygwin - the
> person and the person's company who makes the changes must
> have a signed agreement with Red Hat.

I'm not talking specifically about Cygwin, but it would be to
everybody's benefit if we could figure out how to incorporate
public domain software without getting the lawyers all riled
up(*). This stuff is being donated to the greater infosphere
for the common good--there should be a way to Do The Right
Thing (tm) and actually have it count.  :-)

gsw

(*) - I was really thinking of a much more colorful metaphor
      as I wrote this.

             reply	other threads:[~2006-05-30 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 14:04 Williams, Gerald S (Jerry) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-25 13:45 Williams, Gerald S (Jerry)
2006-05-25 13:55 ` Dave Korn
2006-05-25 14:35   ` Christopher Faylor
2006-05-26  5:21     ` Joe Smith
2006-05-26  5:40       ` Christopher Faylor
2006-05-24 16:05 Williams, Gerald S (Jerry)
2006-05-24 16:34 ` Dave Korn
2006-05-24 16:38   ` Christopher Faylor
2006-05-24 16:52     ` Dave Korn
     [not found] <4C89134832705D4D85A6CD2EBF38AE0F3E0956@PAUMAILU03.ags.agere.com>
2006-05-24  9:31 ` Dave Korn

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=4C89134832705D4D85A6CD2EBF38AE0F3E0B33@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).