From: Warren Young <wyml@etr-usa.com>
To: cygwin-apps@cygwin.com
Subject: Re: Changing Setup's license to GPLv3+
Date: Thu, 21 Jan 2016 22:55:00 -0000 [thread overview]
Message-ID: <C915A13E-77E3-42DC-8D72-D0CF0BEC4C66@etr-usa.com> (raw)
In-Reply-To: <20160121104928.GA30823@calimero.vinschen.de>
On Jan 21, 2016, at 3:49 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>
> does anything speak against switching Setup's license to GPLv3+?
> If nobody complains, I'll bump to v3+ in a week or so.
Can you actually do that, legally? I thought the copyright assignments only applied to the DLL, not to setup.exe, so all setup.exe contributors retained their copyright.
That’s what I was told by cgf back when I did my assignment prior to contributing some work to the tar handling, way back when Robert Collins was the lead on the project. cgf said I didn’t need to go to that trouble after I’d already sent it in.
I can’t say I’m wild about GPLv3, for reasons which don’t have to be rehashed here, being well-documented already:
https://en.wikipedia.org/wiki/GNU_General_Public_License#GPLv3_separates_community_further
What actual problem are you trying to solve with the change?
next prev parent reply other threads:[~2016-01-21 22:55 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 [this message]
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
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=C915A13E-77E3-42DC-8D72-D0CF0BEC4C66@etr-usa.com \
--to=wyml@etr-usa.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).