public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Joe Smith" <unknown_kev_cat@hotmail.com>
To: cygwin-talk@cygwin.com
Subject: Re: Re: Handling special characters (\/:*?"<>|) gracefully
Date: Fri, 26 May 2006 05:21:00 -0000	[thread overview]
Message-ID: <e5637u$emi$1@sea.gmane.org> (raw)
In-Reply-To: <20060525143449.GC12123@trixie.casa.cgf.cx>


"Christopher Faylor" <cgf-no-personal-reply-please@cygwin.com> wrote in 
message news:20060525143449.GC12123@trixie.casa.cgf.cx...
> On Thu, May 25, 2006 at 02:55:24PM +0100, Dave Korn wrote:
>>On 25 May 2006 14:45, Williams, Gerald S (Jerry) wrote:
>>>The code was released as PD, so there are no copyrights claimed.  Once
>>>you get a copy, you can do whatever you want with it.
>>
>>Well, I'm not 100% sure that means I can re-license it.  And IIUIC I
>>would need to actually *own* the copyright on anything that I want to
>>place under GPL.  So cgf's caution is probably correct and I should
>>really do a clean-room implementation of my own.
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.

There is considerable precident in the publishing industry to back this up.



>>
>>I think it'll be ok to use the list of functions that you suggested as
>>the basis, however!
>
> FWIW, Red Hat's legal department (who no longer respond to my email) once 
> told
> me that incorporating public domain stuff into Cygwin was ok as long as it 
> was
> very clear that there was no claim on the code
>
> Unfortunately, proving that a company doesn't claim ownership is usually 
> roughly
> equivalent to having them fill out the idious cygwin assignment so, 
> AFAICT, this
> isn't usually all that useful an option to pursue.
>


I suspect that if Jerry were to post a scan of a signed document indicating 
that the company does not claim authorship,
or that the company has placed the work into the public domain, it would be 
difficult for the company to claim
they did not. Now, that should really be acompanied by a similar document 
indicating that
Jerry does not claim rights to the work, as Jerry could potentially have 
some claim to the work.
For example it is possible that the contract that gave the company any claim 
to the work was never
valid in the first place. Highly unlikely, but theoretically possible.

DISCLAMER: IANAL, but I spend a lot of time reading Debian-legal, so I have 
a fairly good understanding of
how copyright works.


  reply	other threads:[~2006-05-26  5:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2006-05-26  5:40       ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2006-05-30 14:04 Williams, Gerald S (Jerry)
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='e5637u$emi$1@sea.gmane.org' \
    --to=unknown_kev_cat@hotmail.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).