Comment by evanelias
13 hours ago
> You can change it, but only going forward.
I don't believe this is correct in this case; realistically, I don't think they can change it at all. As far as I can tell, the WordPress contribution process doesn't involve a CLA or CAA.
That means any license change for WordPress would require getting agreement from every single third-party contributor whose code is still present in the codebase; and/or, removing or rewriting code where the contributor (copyright holder) does not agree. In practical terms, that isn't going to be possible.
WordPress itself is also a fork, which further impacts the situation if any ancient b2/cafelog code is still present in the codebase.
The key point here is that without a CAA, third-party contributors still own the copyright to their code contributions; and without a CLA, the project owner has no legal authority to re-license that third-party code in ways which violate the contributors' license.
The "change it going forwards" thing generally only applies if a CLA or CAA was used; or if the previous license was a permissive one and the new license terms don't violate the old license terms in any way.
Gotcha. Yea, in that case it’s difficult. You can only change the license for things you created, and only for new code. If Wordpress has mixed in contributions from a lot of other people, then it’s impossible in practice to get permission from all of them (and some might even be dead).
In practical terms as long as no one sues they can do anything they want, if enough money on the table then yeah, someone's going to sue, and WP greatly meets that bar.
Had a project I was a major contributor on relicensed to appease microsoft of all things and I just didn't care enough to do something about it besides tell the person they were an asshole.