LXD now re-licensed and under a CLA
stgraber.org
LXD now re-licensed and under a CLA
1–10 of 102 posts
Re: LXD now re-licensed and under a CLA
#2Re: LXD now re-licensed and under a CLA
#3Re: LXD now re-licensed and under a CLA
#4Re: LXD now re-licensed and under a CLA
#5[deleted]
> 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.
Re: LXD now re-licensed and under a CLA
#6[deleted]
You, too, are wrong. From Canonical's actual announcement: > 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.
Re: LXD now re-licensed and under a CLA
#7[deleted]
If the current title isn't accurate, and anyone can suggest a more accurate and neutral one, we can change it again.
Re: LXD now re-licensed and under a CLA
#8[deleted]
You, too, are wrong. From Canonical's actual announcement: > 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.
What Stephane was complaining about is the whole Snap package for lxd has been marked as AGPL, and that's not correct.
Check in the store, down, in the license info section:
Edit: also, from what I see in the commit, it doesn't make much distinction between what's AGPL and what not. https://github.com/canonical/lxd/pull/12663/commits/b8ff449d...
Re: LXD now re-licensed and under a CLA
#9[deleted]