Not logged in
Log in now
Create an account
Subscribe to LWN
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
FOSDEM: Richard Fontana on copyleft-next
Posted Feb 23, 2013 23:58 UTC (Sat) by dlang (✭ supporter ✭, #313)
Just like the 'anti-tivo' clause in GPLv3 did a lot to cause the split in developers, this 'anti-mysql' clause in this license will split developers as well
If your purpose is to divide the community further, then go ahead.
but if you want to unify the community drop this clause
Posted Feb 24, 2013 2:19 UTC (Sun) by rahulsundaram (subscriber, #21946)
Besides your argument is too simplistic. BSD communities don't prefer any copyleft licenses at all so even GPLv2 was very divisive for them. So we have to ask ourselves, what is the target of the license and which communities are we helping?
Posted Feb 24, 2013 3:29 UTC (Sun) by rfontana (subscriber, #52677)
There is a big difference between the copyleft-next provision and the
anti-lockdown provision of GPLv3. The copyleft-next provision works by
granting additional freedom to downstream users (freedom for everyone
to escape copyleft, giving everyone an equal right to create
proprietary derivative works rather than monopolizing that right in
the upstream licensor). The GPLv3 provision imposes an additional
requirement on downstream distributors (beyond pre-GPLv3 consensus
understanding of GPL copyleft requirements). So the comparison seems
odd to me.
> If your purpose is to divide the community further, then go ahead.
> but if you want to unify the community drop this clause
This makes it sound as though there is a sizable "community" of people
who are thrilled or enthusiastic about copyleft/proprietary
dual-licensing/open core business models. I see no evidence that such
a community exists. The effect of this provision will simply be that
those who wish to extend the life of this peculiar legacy use of
copyleft will continue to use the licenses that are being used for
this purpose today.
Posted Feb 25, 2013 21:40 UTC (Mon) by dlang (✭ supporter ✭, #313)
they used almost the exact same language you are using to defend that provision
Posted Feb 26, 2013 2:46 UTC (Tue) by rfontana (subscriber, #52677)
GPLv3 section 6 states that the anti-lockdown provision does not apply
"if neither you nor any third party retains the ability to install
modified object code on the User Product".
In other words, the policy problem the anti-lockdown provision was
aimed at (by the time of its reformulation in public Draft 3 of GPLv3)
was the asymmetry of upstream (or some third party) being able to
install modified versions on the user's device, with the user being
technically thwarted from exercising a similar freedom to install
modified versions on the user's device.
In the copyleft-next provision, the original licensor is effectively
saying "If I get to create proprietary derivative works, then you
ought to have the same right to create proprietary derivative works".
There's also an equality principle underlying some of the GPLv3 patent
provisions that have no counterpart in copyleft-next.
So, yes, principles of equality and nondiscrimination are part of the
legacy of the GPL family (and I suppose FLOSS licenses generally), but
different licenses implement those principles in different ways. For
example, pure non-copyleft licenses say "everyone getting *this* copy
gets an equal right to create proprietary derivative works".
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds