public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: cygwin-licensing@cygwin.com
Subject: Re: Help! Need B.20.1 src
Date: Thu, 27 Jan 2005 12:23:00 -0000	[thread overview]
Message-ID: <20050127121327.GQ31117@cygbert.vinschen.de> (raw)
In-Reply-To: <1106801478.5890.13.camel@mellor.kw.net>

On Jan 26 23:51, John Mellor wrote:
> On Sun, 2005-23-01 at 16:03 +0100, Corinna Vinschen wrote:
> > You have two choices:
> > 
> > - Comply with the GPL in one way or the other, which always means your
> >   application is also GPLed and you have to open the source code to
> >   your customer.
> > 
> > - Or, you ask Red Hat for a special Cygwin License according to this
> >   paragraph on http://cygwin.com/licensing.html:
> > 
> >     Red Hat sells a special Cygwin License for customers who are unable
> >     to provide their application in open source code form. For more
> >     information, please see: http://www.redhat.com/software/cygwin/,
> >     or call +1-866-2REDHAT ext. 45300 (toll-free in the US)
> 
> Thanks for the clarification.  Yes, I read that incorrectly.
> 
> I have no problem passing on the full source code to the Customer (after
> all, that's what they paid me to work on), but I can't pass it on to
> other parties as it contains some code fragments that implement their
> trade secrets, and doing so would violate the trade secrecy laws.
> 
> So, am I safe if I give the Customer the source for an app that is
> linked against cygwin1.dll, but not also publish it to the whole world?

Yes.  The GPL requires you to open the sources (of your application
*and* of Cygwin) to the audience.  If the audience is only one customer,
then giving the sources to this one customer is fine. 

But keep track that your customer doesn't release the application to
their customers.  In that case, these customers inherit the natural right
to get the sources as well!  If that's not an option, your customer will
have to fall back to purchasing a commercial Cygwin license.

One additional hint: The GPL requires that the audience is able to
rebuild the exact version of the application.  This means, you must
provide the exact same source version from which you've build your
application to your customer.  This rule applies to the Cygwin version
as well.  If you're providing Cygwin 1.5.12 with your application, then
you have to provide also the sources of Cygwin 1.5.12.  So it's always a
good idea to pull also the source package of Cygwin from the mirror
immediately, if you're providing a package which includes Cygwin.

Please let's move any further discussion to cygwin-licensing@cygwin.com.
I've Cc'd my reply to that list.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.

      parent reply	other threads:[~2005-01-27 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1106432621.23759.6.camel@mellor.kw.net>
     [not found] ` <20050122234445.GI32005@trixie.casa.cgf.cx>
     [not found]   ` <1106442000.24143.20.camel@mellor.kw.net>
     [not found]     ` <41F2FB38.BD37B3FB@dessent.net>
     [not found]       ` <20050123012249.GN32005@trixie.casa.cgf.cx>
     [not found]         ` <1106490525.32550.9.camel@mellor.kw.net>
2005-01-23 17:18           ` Christopher Faylor
     [not found]           ` <20050123150354.GC10176@cygbert.vinschen.de>
     [not found]             ` <1106801478.5890.13.camel@mellor.kw.net>
2005-01-27 12:23               ` Corinna Vinschen [this message]

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=20050127121327.GQ31117@cygbert.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-licensing@cygwin.com \
    --cc=cygwin@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).