From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin-licensing@cygwin.com>
Subject: RE: Licensing/Installer Questions
Date: Fri, 03 Mar 2006 15:51:00 -0000 [thread overview]
Message-ID: <041a01c63ed8$d7eb2dd0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060303124001.GU3184@calimero.vinschen.de>
On 03 March 2006 12:40, Corinna Vinschen wrote:
> 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
In case you choose to skip or skim my rather more verbose mail, it basically
says the same as Corinna has written here, but I think there's one extra
point:
> - 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.
I think the GPL is generally read as implying that those sources must be
provided on a physical medium.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-03-03 15:51 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
2006-03-03 15:51 ` Dave Korn [this message]
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='041a01c63ed8$d7eb2dd0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.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).