unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Evan Weaver <evan@cloudbur.st>, "Zed A. Shaw" <zedshaw@zedshaw.com>
Subject: Re: adding GPLv3 to unicorn license
Date: Sat, 20 Aug 2011 21:45:17 +0200	[thread overview]
Message-ID: <CALiegfkkzJ3CL_pgdr5bCnu3efmxzg4pYws305C=GvNWUWbSQQ@mail.gmail.com> (raw)
In-Reply-To: <20110428005727.GA19557@dcvr.yhbt.net>

2011/4/28 Eric Wong <normalperson@yhbt.net>:
> Hello, I would like to extend the unicorn license from
> (GPLv2|Ruby terms) to (GPLv2|GPLv3|Ruby terms).
>
> Zed and Evan are still the authors of much of the HTTP parser code in
> unicorn and some of the tests, so I'm asking you guys first.  I would
> also like to license kcar[1] in the same way since it's a fork of
> the unicorn parser (for client-side usage).
>
> Adding GPLv3 would allow AGPLv3-only applications to be bundled with
> unicorn and distributed.  This would be useful for people distributing
> complete devices running AGPLv3 apps on unicorn.
>
> I'm a supporter of strong copyleft licenses and I want unicorn to
> be distributable with applications with strong copyleft licenses.
>
> Furthermore, I (or whoever replaces me as project leader when I die)
> would like to have the option of adding compatibility for newer versions
> of the GPL (as published by the FSF).  I'm /not/ asking for a "GPLv2 or
> later" clause since that would give the FSF too much power for GPLv4.
>
> I'm not at all interested in adding licenses other than future versions
> of the GPL.  Even though I support AGPLv3 for user-facing applications,
> I do /not/ want infrastructure like unicorn to be under the terms of
> something like the AGPLv3.
>
> I'll email the other contributors who have more trivial contributions if
> you guys agree.  Thanks!

Hi, I'm fine with it, fully.

Cheers.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>
_______________________________________________
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

      parent reply	other threads:[~2011-08-20 19:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28  0:57 adding GPLv3 to unicorn license Eric Wong
2011-04-28  0:59 ` [RFC/PATCH] LICENSE: add GPLv3 to license terms Eric Wong
2011-05-16 21:54 ` adding GPLv3 to unicorn license Eric Wong
2011-05-16 22:03   ` Eric Wong
2011-05-16 22:10     ` Eric Wong
2011-05-16 22:39     ` Luis Lavena
2011-05-16 23:20       ` Eric Wong
2011-05-17  4:45     ` Hongli Lai
2011-08-24  2:56     ` Eric Wong
2011-08-29 20:08       ` Eric Wong
2011-08-20 19:45 ` Iñaki Baz Castillo [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='CALiegfkkzJ3CL_pgdr5bCnu3efmxzg4pYws305C=GvNWUWbSQQ@mail.gmail.com' \
    --to=ibc@aliax.net \
    --cc=evan@cloudbur.st \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=zedshaw@zedshaw.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.
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).