Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Cc: Graham Hughes <graham-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org>
Subject: adding GPLv3 to license
Date: Tue, 10 May 2011 15:07:15 -0700	[thread overview]
Message-ID: <20110510220715.GA8949@dcvr.yhbt.net> (raw)

I'm going to add GPLv3 to the Rainbows! license so it'll be changed
from: Ruby terms + GPLv2
  to: Ruby terms + GPLv2 + GPLv3

This will eventually allow Rainbows! to be combined and distributed with
GPLv3-only and AGPLv3 packages without a potential license conflict.

I'm also reserving the ability to add future versions of the GPL (as
published by the Free Software Foundation) to the license.  I will not
be have a "GPLv2 or later" clause since I don't want the FSF to upgrade
the license without my review.  Even though I like the AGPL for web
/applications/, I don't think it's appropriate for infrastructure such
as Rainbows!.

Graham (Cc-ed) is the only contributor to Rainbows! other than myself,
and his patch[1] was only trivial bugfix which shouldn't prevent me
from making a minor change to the license.

Rainbows! depends on Unicorn, and Unicorn (and Mongrel) has more
contributors and thus harder to add the GPLv3 to...

[1] bogomips.org/rainbows.git/patch?id=a34b1048d05397f72ad579fcef72cbb1a9e9d8bc

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


                 reply	other threads:[~2011-05-10 23:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110510220715.GA8949@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=graham-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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/rainbows.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).