You can't have it both ways.
Posted Sep 26, 2006 11:47 UTC (Tue) by
hummassa (subscriber, #307)
In reply to:
GPLv3 & additional permissions/restrictions by mingo
Parent article:
Some GPLv3 clarifications from the FSF
Either the additional terms clause 7 will cause "balkanization" or it will cause "trending-to-purification", and your argument is just swinging between those instances.
You are right that clause 7 is biased towards "purification". And that is intentional IMHO, so "balkanization" is less likely to occur. If you can compatibilize "things with additional permisisons" with "things with no additional permissions" under the "things with no additional permissions" umbrella, then balkanization is not occurring (at least from the point of view of "things with no additional permissions".) OTOH, if you can compatibilize "things with (some, restricted) additional requirements" with "things with no additional requirements" under the umbrella of "things with additional requirements, that don't apply to the whole body equally". Which, although not as simple, is not very different from the situation today, applied to multi-holders, multi-license systems like the the linux kernel (that has BSD/2clauses code, BSD/3clauses code, v2-only code, v2+ code...)
So, yes, there is a bias in clause 7 towards the distribution of works under the "pure" v3 conditions. But this is really intentional.
(
Log in to post comments)