@vovafeldman I have brought up this issue for discussion on the #plugins-review channel, and I concluded there are basically two options:
- WordPress changes its license to BSD or something else, not copyleft, for future versions
- WordPress, as the copyright holder, assumes that plugins are separate work (not a derivative work) as per the GPL2 interpretation, thus not bound to GPL2 license. They can still require plugins to be GPL compliant to be listed on the WordPress Plugin Directory.
I don’t know if option number 2 has legal grounds, though. I’m not sure if someone can say otherwise, even if WordPress assumes this instance.
If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works.
Either way, by the looks of the conversation I had on Slack, it is clear that WordPress employees that get paid top-notch salaries for working on GPL2 software are not so keen to the calvary of WordPress shops such as ourselves - we either mobilize the WordPress companies environment for a solution, or nothing will change.
Here’s the link to the #plugins-review discussion I cite on this answer, which has interesting arguments: https://wordpress.slack.com/archives/C1LBM36LC/p1607960096262300
Edit: I have posted about this on the Advanced WordPress Group, feel free to continue this conversation here or there: https://www.facebook.com/groups/advancedwp/permalink/3775755309153322