RFC: Moving the Godot Card Game Framework to an MIT License - eviltoast

I’ve started the CGF some years ago to learn Godot and to provide something to the community. I even made a few FOSS games with it.

Sadly my work with my other FOSS projects and the fediverse doesn’t give me enough time to keep it up to date and to migrate it to Godot 4 and since the engine is picking up a ton of speed, I think it’s a shame people have to keep rediscovering the card game wheel.

I know a lot of people avoid it due to the AGPL3 license, so I am thinking of switching to an MIT license instead in the hopes that others will help carry the torch until I find time to circle back to it. There’s always pitfalls with MIT of course, such as some company trying to enclose it and sell it as a service, but perhaps peer pressure would be enough of a deterrent at this time.

Anyway. Just opening this up for discussion.

  • RobotToaster@mander.xyz
    link
    fedilink
    arrow-up
    11
    ·
    6 months ago

    I’m not a gamedev, but have you considered LGPL? My understanding is it allows the use of the library in proprietary software, but still requires improvements to the library itself to be released (although without the network requirement)

    • db0@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      7
      ·
      6 months ago

      The problem is that the CGF is not an external library, it’s becomes core part of the game. Also for people who care about this stuff, so long as the “GPL” part is there, they don’t touch it either.

    • anlumo@feddit.de
      link
      fedilink
      arrow-up
      5
      ·
      6 months ago

      The LGPL is inherently incompatible with anything on Apple’s App Store, so if there’s a chance that I might want to publish it there I can’t touch anything-GPL.

      • tabular@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        6 months ago

        I get what you mean but at face value that sounds like LGPL is the issue, rather than Apple.

        • anlumo@feddit.de
          link
          fedilink
          arrow-up
          2
          ·
          6 months ago

          Depends on your point of view. Legally it definitely is, because the LGPL stipulates that nobody is allowed to attach any restrictions on to the code above the things the LGPL restricts itself. This makes it impossible to combine with the App Store, because that store adds additional restrictions.