From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: [PATCH] license: allow all future versions of the GNU GPL
Date: Sat, 26 Oct 2013 10:09:52 +0000 [thread overview]
Message-ID: <20131026100952.GA13096@dcvr.yhbt.net> (raw)
In-Reply-To: <CAM3ce8FD=EqhfT6Dqc9JEENfmFPHD-1YBA_EXLr57r+aq9NC8w@mail.gmail.com>
Hongli Lai <hongli@phusion.nl> wrote:
> On Sat, Oct 26, 2013 at 9:58 AM, Eric Wong <normalperson@yhbt.net> wrote:
> > There is currently no GPLv4, so this change has no effect at the
> > moment.
> >
> > In case the GPLv4 arrives and I am not alive to approve/review it,
> > the lesser of evils is have give blanket approval of all future GPL
> > versions (as published by the FSF). The worse evil is to be stuck
> > with a license which cannot guarantee the Free-ness of this project
> > in the future.
> >
> > This unfortunately means the FSF can theoretically come out with
> > license terms I do not agree with, but the GPLv2 and GPLv3 will
> > always be an option to all users.
>
> Don't you need approval from all contributors, including Zed, to be
> able to do something like this?
I already got this a few years ago when I got permission for the GPLv3:
- The unicorn project leader (Eric Wong) reserves the right to add future
- versions of the GPL (and no other licenses) as published by the FSF to
- the licensing terms.
So I'm adding all future versions of the GPL.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
prev parent reply other threads:[~2013-10-26 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 7:58 [PATCH] license: allow all future versions of the GNU GPL Eric Wong
2013-10-26 9:54 ` Hongli Lai
2013-10-26 10:09 ` Eric Wong [this message]
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
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131026100952.GA13096@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
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).