public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Luke Kendall <luke.kendall@cisra.canon.com.au>
To: The Cygwin Mailing List <cygwin@cygwin.com>,
	<cygwin-licensing@cygwin.com>
Cc: audit <audit-mail-disclaimer@cisra.canon.com.au>
Subject: Re: Cygwin now licensed under GPLv3+
Date: Tue, 13 Sep 2011 04:44:00 -0000	[thread overview]
Message-ID: <4E6ED010.7040300@cisra.canon.com.au> (raw)
In-Reply-To: <20110419171444.GF23804@calimero.vinschen.de>

Corinna Vinschen wrote:
> Hi Cygwin friends and users,
>
>
> I'm happy to announce that, effective immediately, Red Hat has
> relicensed Cygwin from "GNU Public License version 2" (GPLv2) to
> "GNU Public License version 3 or later" (GPLv3+).
>
>   

What does that mean in terms of Cygwin components?  Each component 
normally has its own license, so does the above statement mean that 
things like the Cygwin DLL and other Cygwin-only components are under GPLv3?

Is there an explicit list or a precise description of what parts of 
Cygwin are covered by GPLv3?

Regards,

luke

> The Open Source Licensing Exception persists, as well as the
> availability of the Cygwin Alternative License, as described on
> http://cygwin.com/licensing.html
>
> This shouldn't affect a lot of you, but if you're concerned that this
> change in the Cygwin license might affect you and your projects, see
> http://www.gnu.org/licenses/ in the first place.  You can also ask
> questions on the cygwin or cygwin-licensing mailing list, but be aware
> that we can't give valid legal advice.  It's always better to ask
> a lawyer who's specialized in licensing questions.
>
>
> Have fun,
> Corinna
>
>
> *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
>
> If you want to unsubscribe from the cygwin-announce mailing list, look
> at the "List-Unsubscribe: " tag in the email header of this message.
> Send email to the address specified there. It will be in the format:
>
> cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com
>
> If you need more information on unsubscribing, start reading here:
>
> http://sourceware.org/lists.html#unsubscribe-simple
>
> Please read *all* of the information on unsubscribing that is available
> starting at this URL.
>
>
>   

       reply	other threads:[~2011-09-13  4:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110419171444.GF23804@calimero.vinschen.de>
2011-09-13  4:44 ` Luke Kendall [this message]
2011-09-13  4:58   ` Christopher Faylor
2011-09-13 15:28     ` Luke Kendall
2011-09-13 15:38       ` Christopher Faylor
2011-10-20  7:35 Luke Kendall
2011-10-20  7:49 ` Corinna Vinschen

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=4E6ED010.7040300@cisra.canon.com.au \
    --to=luke.kendall@cisra.canon.com.au \
    --cc=audit-mail-disclaimer@cisra.canon.com.au \
    --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).