> MySQL is the poster child for the behaviour you are against, just
> like Tivo was the poster child for the behaviour that the FSF was
> against when writing that clause in the GPLv3.
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.