• RandoCalrandian@kbin.social
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    is AGPLv3

    Hey, you’re right!

    To get around that they’d have to do something drastic, like getting the owner of the code to change the license in next release, and keep him in an NDA while doing so in order to position themselves when the change happens.

    Good thing we’re not seeing that

    • dan@upvote.au
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      getting the owner of the code to change the license in next release

      AFAIK, all contributors need to agree in order to change the license of a codebase. If a contributor disagrees, their part of the code has to be rewritten in order to comply.