So, I started working on a new project, and I’m thinking of how to license it. Specifically, how to make it as copyleft as possible without making it unusable.

By unusable I mean the license blocking the game (or in a more likely case, any later project that reuses the code) from being published on platforms like Steam. I know that steamshim exists, but I’m not sure if that can be a real solution. Linking against the SDK seems completely optional in Steam’s case, but license compatibility is listed as a hard requirement regardless.

The game code consists entirely of a GDExtension written in Rust, so I think I can just neatly LGPL the GDExtension “library” without restricting the game executable itself. It sounds like it should work, but there are some things that I’m not sure of, like hardcoded references to assets.

I really don’t enjoy thinking licenses so I usually slap on either GPL or something permissive and be done with it. Anyone notice any holes in my plan, or am I good to go?

I know I can use my own code however I please, but it gets more difficult once there are multiple people involved; I’ve had one person express vague interest so far.

Thanks.

  • toothbrush@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    5
    ·
    3 天前

    You can “dual license” your code, proprietary and whatever strong copyleft you prefer. For users, it means copyleft, and for steam it means your code is compatible.

    • fum@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      3 天前

      I believe this would require agreement from all contributors, or for them to sign some kind of contributor licence agreement.