[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#238245: license choice - consensus on dual MIT/GPL-2 ?

On Wed, 18 Jan 2012 13:09:21 +0100 Stefano Zacchiroli wrote:

> On Wed, Jan 18, 2012 at 12:38:01AM +0200, Andrei Popescu wrote:
> > Not sure I understand: if this goes through will all material be 
> > dual-licensed or it's just that everybody chooses one of the two 
> > licenses and as a consequence the whole site is dual-licensed (as an 
> > aggregate work)?
> The former: people will need to agree to re-license their contributions
> under dual MIT/GPL-2 license; in the end each contribution, as well as
> the website as a whole [1], will be dual-licensed.
> [1] modulo specific exceptions, like the one mentioned by Alexander

First of all Stefano, thanks for trying to gain consensus on the target
license for the re-licensing!

However, I think you should clarify what you mean by "dual-licensing".

"Dual-licensing" is usually intended to mean that both licenses are
being offered and the recipient of the work may choose either one,
according to his/her own preferences.
If this is what you mean, then it should be noted that "dual-licensed
under Expat/MIT and GPLv2+" is effectively equivalent to "licensed
under the Expat/MIT", since the Expat license's permissions are a
superset of GPLv2+ license's ones, and Expat license's restrictions
are a subset of GPLv2+ license's ones.
Hence, I would suggest dropping the confusing addition of the GPLv2+:
please just ask for consensus on re-licensing under the Expat/MIT
license (while reminding people that this license is indeed

If instead, by "dual-licensing", you (strangely) mean that the
recipient of the work has to comply with both licenses at the same time,
then your proposal is effectively equivalent to asking for consensus
on re-licensing under the GNU GPL v2 or later.
In this case, I would suggest doing just that, in order to avoid

Please disambiguate: which one is the intended meaning?

 New GnuPG key, see the transition document!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE

Attachment: pgp_aWAKDasue.pgp
Description: PGP signature

Reply to: