Just remembered that the way other #opensource projects dealt with this was by changing their license, avoiding cannibalization by big tech, but at the expense of their community.
-
Just remembered that the way other #opensource projects dealt with this was by changing their license, avoiding cannibalization by big tech, but at the expense of their community.
I can't even imagine what would be of us all if that fool actually moves into that direction.
-
@jbz WordPress Foundation can't retroactively change the license on old versions. Those are out there, they can be (& have been) forked. It would put companies like WP Engine in the business of maintaining a CMS (which given they seem to be in an enshittification spiral, they DO NOT WANT), but they'd be on firm legal footing.
-
@FeralRobots @jbz As far as i know, they can't relicense for new versions either, at least without clean-room reimplementing some load-bearing parts of the code. Wordpress was originally a fork of a system that i can't remember the name of, which was GPL-licensed and didn't have contributor agreements. So if any of that code still exists in the codebase (and i guarantee that it does), they're locked to a GPL-compatible license.
-