public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: GPLv3
Date: Tue, 03 Jul 2007 07:09:00 -0000	[thread overview]
Message-ID: <20070703070915.GA22925@calimero.vinschen.de> (raw)
In-Reply-To: <46895B87.3060908@users.sourceforge.net>

On Jul  2 15:09, Yaakov (Cygwin Ports) wrote:
> Corinna Vinschen wrote:
> > There are no short-term plans to change the license of Cygwin, rather we
> > just wait until the OSI certifies the GPLv3 as open source license
> > according to the definitions.  As Brian already noted, as soon as the
> > OSI certifies the GPLv3, the exemption clause from
> > http://cygwin.com/licensing.html will also cover GPLv3'ed packages.
> 
> IANAL, but I am a stickler for words, so if I may point out the following:
> 
> There has always been an understanding that a license has to be
> OSI-approved to fall under the exception clause of the Cygwin license.
> But the clause doesn't say "approved by the OSI", rather it says:
> 
> "... a license that complies with the Open Source definition ..."
> 
> Complies according to whom?

Read http://cygwin.com/licensing.html again:

  See http://www.opensource.org/docs/definition_plain.html for the
  precise Open Source Definition referenced above.

Even if the license is not approved, the above definition sets the rules
against which the license is measured.

> Could Red Hat's lawyers take another look at the language and provide
> their opinion on this?

Been there, done that.  Regardless of the exact wording, somebody
who wants to ignore the licensing issue will do anyway.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

  parent reply	other threads:[~2007-07-03  7:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01  3:46 GPLv3 Eric Blake
2007-07-01  4:12 ` GPLv3 Brian Dessent
2007-07-01 14:17   ` GPLv3 Eric Blake
2007-07-01 14:24     ` GPLv3 Eric Blake
2007-07-02  7:40     ` GPLv3 Corinna Vinschen
2007-07-02 14:40       ` GPLv3 Andrew Schulman
2007-07-02 15:18         ` GPLv3 Corinna Vinschen
2007-07-02 15:29           ` GPLv3 Andrew Schulman
2007-07-02 18:04             ` GPLv3 Corinna Vinschen
2007-07-02 20:09               ` GPLv3 Yaakov (Cygwin Ports)
2007-07-02 23:29                 ` GPLv3 Dave Korn
2007-07-02 23:52                   ` GPLv3 Yaakov (Cygwin Ports)
2007-07-03  7:09                 ` Corinna Vinschen [this message]
2007-07-03 17:45                   ` GPLv3 Dave Korn
2007-07-03 18:07                     ` GPLv3 Corinna Vinschen
2007-07-02 20:15               ` GPLv3 Yaakov (Cygwin Ports)
2007-07-05  2:33               ` GPLv3 Eric Blake

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=20070703070915.GA22925@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@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).