X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 743253857801
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=dinwoodie.org
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=adam AT dinwoodie DOT org
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=dinwoodie.org; s=google;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
	bh=0jurHLYvmhSu24bA/eNoosZeC6jLdQQ4S4i1kt1ozEw=;
	b=dQue1ZOuCegU6HG8c8RkZqqAcQ4r34jZSWbKv44NAAVY2k76WlL1/AfTQbAEfxQt8G
	EC+Ncd83t4De2APyb/ZlkVS2sNJuy7EuwFnITYAYUw9I+L2uVDur0zq6++bNa3SAMp0z
	Oycgxr+3QhtCHlILEc8E5W0v2OSMuOHP2oTv8=
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to;
	bh=0jurHLYvmhSu24bA/eNoosZeC6jLdQQ4S4i1kt1ozEw=;
	b=VcjOoaYJPFkOeMbgMIi4KiNclIZtrop3cEzrR8ikdiuavEulq5sWwHqtKcb84snE69
	b7rXQk4jqiLiYg7FehHSPplLPR8ZXiCNcDs9/vLpXOByKqV3RCC2yB2YnLX4xd2OHWEI
	fr2IEqgXjIF7ZJ1BnsTOcfMrZtk29mspKVcQfrB8Xu8n5euHo6O5jFJmA4h4EBlwUEOi
	Zwr+qoqCmcHRYdDVOZpxELUKEAKelbJKUOHGHyhMRwj2qVNhpMOvanAOFwQ+etbppX6c
	dKUrycXBHHDAicj2f802XPFZ8ijaekpePd8JymbTIhWcDuCK0h8GUnuTtVTo2reZ44m9
	Uk1Q==
X-Gm-Message-State:	AOAM532ngJW5IOKHLaynQ90VMsRnlpuqbpw9BU413vjmY0k37SaJtZJP
	/Nr9HmAkVui/z5Cf/SkIvAalco4YmpKkkdIVlYa20TQCKtn0WDvK
X-Google-Smtp-Source:	ABdhPJwHiQG8Jx/KgRRAA7OAJtSd0BsIc+IIx4ib7W1MGyTrWRIpDUbY6h2alX5nQKXLPo/e6d3Fis97ZSg1pkPgXHo=
X-Received:	by 2002:ac8:4cc1:: with SMTP id l1mr22357621qtv.128.1607798703593;
	Sat, 12 Dec 2020 10:45:03 -0800 (PST)
MIME-Version:	1.0
References:	<CAKc5nKHCNj1uqPEHUDERSH_p+FJGLEG=fH7wiTEwzf9nkwQNBw AT mail DOT gmail DOT com>
	<34a5e2b9-5179-c0b6-e8b0-1245e7a4578f AT gmail DOT com> <5FAF85CB DOT 8000705 AT tlinx DOT org>
	<3ff604bf-5016-2f62-bea0-8fd97c3bad0c AT gmail DOT com>
	<DB7PR02MB399642C9DCA3E3463C5F2A97E7C90 AT DB7PR02MB3996 DOT eurprd02 DOT prod DOT outlook DOT com>
In-Reply-To:	<DB7PR02MB399642C9DCA3E3463C5F2A97E7C90@DB7PR02MB3996.eurprd02.prod.outlook.com>
From:	Adam Dinwoodie <adam AT dinwoodie DOT org>
Date:	Sat, 12 Dec 2020 18:44:27 +0000
Message-ID:	<CA+kUOa=7AW3tD5EBtAjBYP8Rn7iEjdeqLC=jWhAowx57R=PPWA@mail.gmail.com>
Subject:	Re: Commercial use of cygwin
To:	"Cygwin (cygwin AT cygwin DOT com)" <cygwin AT cygwin DOT com>
X-Spam-Status:	No, score=-2.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,
	SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On Sat, 12 Dec 2020 at 17:27, Hamish McIntyre-Bhatty wrote:
> Do the points made here also apply to commercial but open-source use of
> Cygwin?
>
> For extra context, I have an application with bundles parts of Cygwin
> and libraries built against Cygwin. None of the source or binaries is
> modified.
>
> I know I at least have to state which packages are included in the
> bundle and provide links to the source for those, but I am not sure if
> it is required that I eg provide a downloadable compressed folder with
> complete source for everything.
>
> Can anyone give me some advice? The work everyone does for Cygwin is
> valuable and I certainly don't intend to claim any of it is mine.

The discussion in this thread so far, as best I can tell, amounts to
"you need to comply with the license agreements in the packages you
distribute". That is definitely the case for commercial open-source
projects as much as it is for anything else.

In my opinion, the safest way to make sure you're compliant is to
provide all the source code for all the binaries you're distributing
in the same way you make those binaries available; if you're shipping
software on CD, ship the source code on the same CD; if you're
shipping software by providing a download link, provide a download
link nearby to the source code. In particular, it's not sufficient to
merely point to the Cygwin website or even Cygwin mirrors, as those
could disappear while you're still legally obliged to provide source
code for at least anything with a GPL/LGPL/&c license.

That all being said, I am not a lawyer, and I have no particular
authority in the Cygwin project to assert what is and isn't
permissible. Particularly for any commercial use, I would want
professional legal advice on anything I wasn't confident about.

HTH

Adam
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -