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: Rsync over ssh (pulling from Cygwin to Linux) stalls..
Date: Fri, 18 Aug 2006 13:31:00 -0000	[thread overview]
Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F683A64@PAUMAILU03.ags.agere.com> (raw)

mwoehlke wrote:
>Williams, Gerald S (Jerry) wrote:
>> Whatever the reason, it interferes with my ability to contribute code
>> to Cygwin even if I can package it separately, since my company will
>> not sign the assignment. They will, however, allow me to release code
>> into the public domain. 
>
> FWIW, my impression is still that *you* could PD your code, and then
> someone else who *can* sign an assignment can come along, make a
> trivial change (like adding a comment, thus qualifying it as a
> "derivative work" that can be copyrighted), and then submit it.

Yes, I alluded to that earlier, although the language
in the assignment may undermine the attempt. Specifically,
you claim that "I hereby represent and warrant that I am
the sole copyright holder for the Work and that I have the
right and power to enter into this contract."

The one time I offered to provide code under this sort of
arrangement, it turned out to be easier to avoid the whole
situation entirely and just have somebody else rewrite the
code. So I never got an answer as to whether this would be
acceptable.

Can anyone from RedHat acknowledge that this arrangement
would be acceptable to them? If so, that would potentially
open the door to any public domain code.

gsw

P.S. Note that I didn't say that it was *impossible* for me
     to contribute code to Cygwin. I'm sure that if I had
     something important enough, we could reach some sort
     of arrangement where my company lawyers would sign an
     assignment that specifically applied to that piece. We
     could probably even dispense with the 30 day written
     notice and release it directly into the public domain
     at the same time. What's not fully clear is whether
     this type of assignment can be applied to code that's
     already in the public domain (regardless of who wrote
     it).

             reply	other threads:[~2006-08-18 13:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 13:31 Williams, Gerald S (Jerry) [this message]
2006-08-18 14:17 ` Dave Korn
2006-08-18 14:26   ` mwoehlke
2006-08-18 14:44     ` Dave Korn
2006-08-18 15:09       ` mwoehlke
2006-08-18 15:45         ` Dave Korn
2006-08-18 15:58           ` mwoehlke
2006-08-18 16:06             ` Dave Korn
2006-08-18 16:42               ` Dave Korn
2006-08-18 18:28               ` Igor Peshansky
2006-08-18 14:43 ` Christopher Faylor
2006-08-18 16:34   ` Williams, Gerald S (Jerry)
2006-08-18 19:28     ` mwoehlke
     [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)
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=4C89134832705D4D85A6CD2EBF38AE0F683A64@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).