{"id":112184,"date":"2023-12-13T15:10:14","date_gmt":"2023-12-13T13:10:14","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/kompaniya-canonical-perevela-proekt-lxd-na-liczenziyu-agplv3"},"modified":"2023-12-13T15:10:14","modified_gmt":"2023-12-13T13:10:14","slug":"kompaniya-canonical-perevela-proekt-lxd-na-liczenziyu-agplv3","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/kompaniya-canonical-perevela-proekt-lxd-na-liczenziyu-agplv3","title":{"rendered":"Canonical has transitioned the LXD project to the AGPLv3 license","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Canonical has released a new version of the container management system LXD 5.20, notable for the change in the project's license and the introduction of a requirement to sign a CLA agreement for transferring ownership rights to the code when accepting changes to LXD. The license for code added to LXD by Canonical employees has changed from Apache 2.0 to AGPLv3, while the code from external contributors, for which Canonical does not hold ownership rights, remains under Apache 2.0. Since Canonical cannot change the license for the entire LXD codebase, the project will now be distributed under mixed conditions \u2014 part of the code under AGPLv3 and part under Apache 2.0. The transition to the new license is explained by the desire to standardize the license with other Canonical server products that use AGPLv3. <\/p>\n
The code from previous releases remains available under the Apache 2.0 license, but all changes made to the re-licensed components will only be published under the AGPLv3 license, which will prevent the fork of Incus from incorporating changes from LXD without converting its codebase to AGPLv3. The Apache 2.0 and AGPLv3 licenses have one-way compatibility, meaning that code under the Apache 2.0 license can be included in code under the AGPLv3 license, but not vice versa. This change signifies a complete cessation of collaboration between the LXD and Incus projects, as the new license hinders the transfer of changes from LXD to Incus, while the necessity of signing the CLA agreement prevents Incus developers from doing so. <\/p>\n
A feature of the AGPLv3 license is the introduction of additional restrictions for applications providing network services. When using AGPL components in the operation of network services, the developer is required to provide users with the source code of all changes made to these components, even if the underlying software is not distributed and is used solely within the internal infrastructure to operate the service. The AGPL license also imposes copyleft conditions, meaning that to include AGPL code from LXD in their project, the codebase of their own project must be re-licensed under the AGPL license. <\/p>\n