• mint_tamas@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 months ago

    What’s the background of the lxd-incus fork? On the project page they just state that it was forked after Canonical took over lxd - but what does that mean, exactly? How did they take over an open project? Was there a technical reason for a fork?

    • anamethatisnt@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      I’d say from a business perspective this is the major thing:
      Real license of LXD

      Per the commit message performing the re-licensing, all further contributions will be under the AGPLv3 license and all contributions from Canonical employees have been re-licensed to AGPLv3.

      However, Canonical does not own the copyright on any contribution from non-employees, such as the many changes they have imported from Incus over the past few months. Those therefore remain under the Apache 2.0 license that they were contributed under.

      As a result, LXD is now under a weird mix of Apache 2.0 and AGPLv3 with no clear metadata indicating what file or what part of each file is under one license or the other.

      This is likely to make it very “fun” for anyone performing licensing reviews to evaluate LXD for adoption in their environment.

      Grabbed from this blog https://stgraber.org/2023/12/12/lxd-now-re-licensed-and-under-a-cla/