Meet the new Embrace, Extend, and Expropriate strategy for Linux?

Remember the concerted smear campaign against Richard Stallman a few years ago in which he was falsely accused of endorsing rape and forced him to resign as president of the Free Software Foundation?

Even then, many assumed that this planned action was preparation for an attack by proprietary software producers on the free software ecosystem. Many did not believe in this (like, “do not attribute ordinary stupidity to malicious intent”), and someone does not believe even now. After all, it is much easier and more convenient to ignore the allegedly non-existent danger, because otherwise you need to somehow respond to it (at least morally).

And now, in Linux kernel release 6.2there has been a very important change – it is allowed to accept code into the Linux kernel under a license Copyleft-Nextwhich is claimed to be compatible with GPLv2, which is confirmed by lawyers from SUSE and Red Hat (who would doubt it?).

This license also contains a proprietary technology rights clause, which makes Copyleft-Next compatible with Apache 2.0 as well. And to ensure full compatibility with GPLv2, the text of Copyleft-Next explicitly states that a derivative work can be distributed not only under the original Copyleft-Next license, but also under the GPL license.

But as they say, “there is a nuance.”

The Copyleft-Next license contains a clause to automatically revoke copyleft code requirements after 15 years. In other words, after 15 years, the term “Copyleft” on the license copyleft-Next turns into a pumpkin, and the source code can be used already without taking into account the requirements of the GPL, including without the mandatory inheritance of licenses and freedoms for the user in derivative works. In fact, this is a direct road to proprietary firmware based on the Linux kernel, without regard to any requirements and restrictions of the GPL!

I wonder if history likes to repeat itself? In fact, the Copyleft-Next license implements the long-established strategy “Support, build on and destroy”, albeit in a slightly modified version, which would be more correctly called “Support, build on and capture”.

And what do you think now, the persecution planned several years ago to discredit Stallman and preparations for the abolition of the Copyleft principle in the Linux kernel, are these links in the same chain? Or is it easier to reassure yourself again with Argumentum ad ignorantiam explanations, conspiracy theories and other “non-existent” horror stories?