Introduction The LXD team would like to announce the release of LXD 5.20! Thank you to everyone who contributed to this release! LXD change to AGPLv3 Canonical has decided to change the default contributions to the LXD project to AGPLv3 to align with our standard license for server-side code. All Canonical contributions have been relicensed and are now under AGPLv3. Community contributions remain under Apache 2.0. We follow the Software Freedom Law Center guidance in relation to this. Going ...
No, it comes together with a CLA being required to contribute. In other words, Canonical (and only Canonical) is still allowed to sell exceptions to the AGPL.
Quite the same case as with matrix. I very much prefer AGPL over all the other permissive licences, but I don’t know, the CLA leaves a bad taste in the mouth
I tried reading through it and I don’t understand completely if they reserve the right to relicense in a way that is against the interest of contributor.
They say that the contributor retains the copyright and can do whatever they want with the code they contributed, which is good, they also say that they can sublicense your contributions, which, as far as I know, means they couldn’t make it more permissive, but only more restrictive, at least that is the case with Creative Commons
Is this a based move? From Canonical? (°0°)
No, it comes together with a CLA being required to contribute. In other words, Canonical (and only Canonical) is still allowed to sell exceptions to the AGPL.
Yes, the post says there is no copyright assignment. That’s extremely carefully chosen wording to avoid mention of the CLA which was made required in the same commit as the license change. It’s “just” a super extended license that lets them do whatever, not assignment.
Quite the same case as with matrix. I very much prefer AGPL over all the other permissive licences, but I don’t know, the CLA leaves a bad taste in the mouth
Can somebody explain in a few words what’s CLA? Does it limit contributors rights?
You sign over your copyright on your contributions to the project.
Shit that’s awful, so they could theorically change the lisence to whatever they want at any time
I tried reading through it and I don’t understand completely if they reserve the right to relicense in a way that is against the interest of contributor.
They say that the contributor retains the copyright and can do whatever they want with the code they contributed, which is good, they also say that they can sublicense your contributions, which, as far as I know, means they couldn’t make it more permissive, but only more restrictive, at least that is the case with Creative Commons