• snaggen@programming.dev
    link
    fedilink
    arrow-up
    44
    arrow-down
    3
    ·
    edit-2
    8 months ago

    If you think this is bad, then you should make sure to use copyleft licenses.

    EDIT: Just read the details, and it seems that this is just what they did. SSPL is like AGPL with a stronger SAAS is distribution claus. That might not be valid, according to the OpenSource definition, but unless you are planning to modify the code and provide it as SAAS I think this is no a problem.

    • smileyhead
      link
      fedilink
      arrow-up
      4
      arrow-down
      2
      ·
      8 months ago

      This is not as bad as they didn’t make the whole thing totally proprietary. But FOSS community definetly would have to seek for alternarives unfortunetly.

      • Venia Silente@lemm.ee
        link
        fedilink
        English
        arrow-up
        4
        ·
        8 months ago

        Or just keep using the FOSS versions. These license changes by definition can not be retroactive.

          • Venia Silente@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 months ago

            Sure, but in the meantime until a new fork emerges as the spiritual carry-on, you can just freeze the latest good version on your docker-compose and carry on.