From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: Licensing/Installer Questions
Date: Fri, 03 Mar 2006 13:01:00 -0000 [thread overview]
Message-ID: <20060303124001.GU3184@calimero.vinschen.de> (raw)
In-Reply-To: <14083028.1141387286807.JavaMail.chartpacs@mac.com>
On Mar 3 07:01, Michael Banks wrote:
> If we have a link on our website to download our product, which contains a few open-source cygwin tools, then is it OK to have a separate link to download the sources of those tools, just to try and save some bandwidth? Would it be OK to have text on the website like "Our product uses a number of open-source tools. To comply with the licesing for these tools, we are required to provide the source code for them. The source code is available upon request, so please contact us at yyy@zzz.com if interested."
The basic GPL rules are
- The recipient has the right to get the sources the same way as the
binaries. If you provide a binary CD, put the sources onto the same
CD or provide an extra source CD. If you provide the binaries by ftp
or http, provide the sources under the same URL as the binaries. This
is according to GPL section 3a. It's the way Cygwin is provided by us.
- If you don't provide the sources, you must provide a *written* offer,
valid for at least three years, to provide the source code on request.
This is according to GPL section 3b.
Whatever, please note you have to provide the *exact* sources of the
tools provided to the customer. If you send the binary foo, version 1.3
and the customer wants the sources three years later, you must provide
the source of foo-1.3. You must not provide the source for version
foo-2.7, just because that's the most recent version of the project foo
at the time of the request. You are required to keep the sources of the
exact version you provided. I hope that's clear.
However, I can only really suggest to read the GPL closely and to
consult a layer who is specialised in licensing issues. Whatever I tell
you, I'm not a lawyer. As another measurement, I would ask you to
contact Red Hat for any more special questions. For your convenience I
have attached the important links for you:
GPL: http://www.gnu.org/licenses/gpl.html
GPL FAQ: http://www.gnu.org/licenses/gpl-faq.html
Red Hat: http://www.redhat.com/software/cygwin/
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2006-03-03 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 9:17 Michael Banks
2006-03-01 10:02 ` Corinna Vinschen
2006-03-01 14:05 ` Michael Banks
2006-03-01 14:19 ` Corinna Vinschen
2006-03-03 12:17 ` Michael Banks
2006-03-03 13:01 ` Corinna Vinschen [this message]
2006-03-03 15:51 ` Dave Korn
2006-03-03 15:32 ` 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=20060303124001.GU3184@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-licensing@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).