From: Eric Wong <normalperson@yhbt.net>
To: Luis Lavena <luislavena@gmail.com>
Cc: "Suraj N. Kurapati" <sunaku@gmail.com>,
"Iñaki Baz Castillo" <ibc@aliax.net>,
"Andrey Stikheev" <andrey.stikheev@gmail.com>,
"Ian Ownbey" <ian@inspir.es>,
mongrel-unicorn@rubyforge.org,
"Augusto Becciu" <augusto@jadedpixel.com>,
"Wayne Larsen" <wayne@larsen.st>,
"Hongli Lai" <hongli@phusion.nl>
Subject: Re: adding GPLv3 to unicorn license
Date: Mon, 16 May 2011 16:20:14 -0700 [thread overview]
Message-ID: <20110516232014.GA11037@dcvr.yhbt.net> (raw)
In-Reply-To: <BANLkTikg=2M9sNJRf6SdPpXRax2xhW2Ukg@mail.gmail.com>
Luis Lavena <luislavena@gmail.com> wrote:
> I'm OK.
>
> mongrel_service do not fall into Mongrel's licensing I believe.
>
> Also, since is a gem plugin, do not need to comply with GPL licensing,
> correct?
I think so, but Mongrel is has been GPLv2 + Ruby license terms for
years, now.
> If that is the case, then yes, no complains from me.
The Ruby license terms can still be chosen for mongrel_service ever an
issue since Mongrel itself already has the GPLv2 option. I don't plan
on removing the Ruby licensing terms option from the Unicorn license,
ever[1].
This addition only affects Mongrel code that remains in Unicorn, even,
so it doesn't affect Mongrel-only things like mongrel_service.
If Mongrel itself ever wanted to add the GPLv3 to it's license, I'd
of course be in full support to it.
> If that is not the case, then you have my complain. mongrel_service
> uses a library created by myself which is MIT, by turning mongrel and
> mongrel_service into GPL, could affect my usage of this library in
> other projects.
The Ruby-specific terms remain, so I believe mongrel_service is fine.
The GPLv3 option is no more "viral" than the existing GPLv2 option.
> Just saying. Licensing sucks.
Agreed :<
--
Eric Wong
_______________________________________________
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
next prev parent reply other threads:[~2011-05-16 23:20 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 [this message]
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
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=20110516232014.GA11037@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=andrey.stikheev@gmail.com \
--cc=augusto@jadedpixel.com \
--cc=hongli@phusion.nl \
--cc=ian@inspir.es \
--cc=ibc@aliax.net \
--cc=luislavena@gmail.com \
--cc=mongrel-unicorn@rubyforge.org \
--cc=sunaku@gmail.com \
--cc=wayne@larsen.st \
/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).