public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Changing Setup's license to GPLv3+
Date: Fri, 22 Jan 2016 19:14:00 -0000	[thread overview]
Message-ID: <87bn8dqveh.fsf@Rainer.invalid> (raw)
In-Reply-To: <DF9AD75C-A885-4572-96A7-28569801A006@etr-usa.com> (Warren	Young's message of "Fri, 22 Jan 2016 11:57:13 -0700")

Warren Young writes:
>>  I'm not trying to do that single-handedly and without reason.  I'm
>> asking here to reach out to the current active developers.  A switch
>> from GPLv2+ to GPLv3+ works without having to reach out to *all*
>> copyright holder.
>
> I don’t think I agree with that.

"9. Each version [of the GPL] is given a distinguishing version number. If
the Program specifies a version number of this License which applies to
it and “any later version”, you have the option of following the terms
and conditions either of that version or of any later version published
by the Free Software Foundation. If the Program does not specify a
version number of this License, you may choose any version ever
published by the Free Software Foundation."

> Let’s say I write a standalone program and license it under GPLv2+ and
> give you a copy.  You can’t then relicense it under GPLv3 or GPLv3+
> just because I said “or later” in the license.  *I* can relicense it,
> but only because I hold the original copyright.

"2.b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any part
thereof, to be licensed as a whole at no charge to all third parties
under the terms of this License."

> All “or later” gives you the right to do is treat the code *as if* I
> had originally licensed it as v3, and then only if you want to.  This
> lets you link v2+ code to v3.  (But not v2-only code to v3!  More
> below.)

But it does permit this.  That's the whole point of licensing GPLv2+
rather than GPLv2.

> I think you’d still have to get permission from all people who still
> have code in the current setup.exe sources.

The copyright isn't touched in any way and the license the copyright
holders chose expressedly allows the distribution under a later version
of that license.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  parent reply	other threads:[~2016-01-22 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 10:49 Corinna Vinschen
2016-01-21 22:55 ` Warren Young
2016-01-22 16:54   ` Corinna Vinschen
2016-01-22 18:57     ` Warren Young
2016-01-22 19:13       ` Eric Blake
2016-01-22 19:58         ` Corinna Vinschen
2016-01-22 19:14       ` Achim Gratz [this message]
2016-01-22 19:14 ` Achim Gratz
2016-01-24  4:30 ` Yaakov Selkowitz

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=87bn8dqveh.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).