• hperrin@lemmy.world
      link
      fedilink
      English
      arrow-up
      224
      ·
      10 months ago

      You don’t follow the license that it was distributed under.

      Commonly, if you use open source code in your project and that code is under a license that requires your project to be open source if you do that, but then you keep yours closed source.

    • Even_Adder@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      77
      ·
      10 months ago

      He took GPLv3 code, which is a copyleft license that requires you share your source code and license your project under the same terms as the code you used. You also can’t distribute your project as a binary-only or proprietary software. When pressed, they only released the code for their front end, remaining in violation of GPLv3.

      • Miaou@jlai.lu
        link
        fedilink
        English
        arrow-up
        5
        ·
        10 months ago

        Probably the reason they’re moving to a Web offering. They could just take down the binary files and be gpl compliant, this whole thing is so stupid

            • Kusimulkku@lemm.ee
              link
              fedilink
              English
              arrow-up
              3
              ·
              9 months ago

              Yes, I meant more that AGPL was created to plug this particular loophole. As in, if it was AGPL, they couldn’t do this.

              • lad@programming.dev
                link
                fedilink
                English
                arrow-up
                2
                ·
                edit-2
                9 months ago

                That’s true

                Although I personally am not a fan of licences this strict, MIT+Apache2.0 seems good enough for me. Of course, that might change with time and precedents like this 😅