On 08/01/2012 06:06 PM, Bradley M. Kuhn wrote:
The question really is, at least for me
regarding this project's goal : does copyleft-next *only* have a AGPLv3
compatibility provision to avoid the political fallout of not having
one, or is it indeed the real goal of copyleft-next to rise above
license proliferation by making a copyleft true "cross-copyleft
compatible", but simpler, more elegant copyleft? This is what I ask
myself when I look at your AGPLv3 compatibility clause.
You also have to look at "ws-supp". Right now that's just basically
AGPLv3 section 13 paragraph 1 because I haven't dealt with it, but I
intend for it to be a substantial improvement on AGPLv3 (section 13)
(while of course inheriting all the improvements in vanilla
The AGPLv3+/GPLv2+ compatibility clause is partly in vanilla
copyleft-next for political reasons, and partly for policy reasons
(which are political in a different sense).
But there is no general goal to make copyleft-next "cross-copyleft
compatible". I don't think that's necessary. Making it a "simpler,
more elegant copyleft" *is* one of the main goals of copyleft-next. I
could achieve more elegance without that compatibility provision.
But, as I said earlier in this thread, there aren't many RMS'
world, so when I see someone or a group of someones drafting a new
copyleft license or attempting to influence the drafting of such, I end
up having to follow the money and figure out what's really going on,
because copyleft has more enemies than friends. And its enemies are
well-funded and have good, expensive lawyers.
I hear you. Keep in mind the significance of the ex-Harvey Birdman
Rule, imperfect as it is. I've thought about the idea of having a
"disclose potential conflicts of interest" rule.
> Zooko's TGPPL, discussed earlier on this list, was an earlier
> of this development.
As one of the critics of TGPPL, I was very clear throughout that
non-compatibility with FSF's license suite was my only complaint.
there be use to copyleft-next for Zooko and I to finally sit down and
*write* the AGPLv3 additional permission that makes TGPPL? Would that
help inform the copyleft-next project?
Well, any additional permission on AGPLv3 that makes TGPPL is likely
to be easily adaptable to copyleft-next.