I’m starting to work on a C library, and I am having trouble choosing a license, so I need some help.

Keeping in mind that:

  • I want as many people as possible to be able to use my lib, without them worrying about license compatibility, both for libre and proprietary programs;
  • My lib is designed to be statically linked, so its license must allow static linking without compromises;

But, also:

  • I want for whoever uses my lib to credit me: I think mentioning my library’s name, optionally with an URL to my repo and the license text copypasted, in the final software’s documentation / credit page / whatever would be enough;
  • I want for people that make changes to my library, and then use the modified version in their program, be it free or proprietary, to publish the modified source code of my library, under my license (but they can keep the rest of their program under whatever license they want).

What license should I choose? I really have no idea.
I think that if I only cared about the first 3 points, I could choose MIT, but considering the last one?

    • octtOP
      2·
      2 years ago

      Because it explicitely doesn’t grant patent rights.

      Just a few weeks ago, Fedora tackled this issue by announcing the stop on accepting CC0 (license that is actually really popular for software, in comparison to CC BY-SA) software: https://www.theregister.com/2022/07/25/fedora_sours_on_creative_commons/

      All Creative Commons licenses have this issue, not only CC0, including CC BY-SA.

      • RoboHack@lemmy.ca
        1·
        2 years ago

        Patent rights don’t apply to me as much – I live in Canada, and though it’s a bit more complicated than I let on here, we effectively don’t have software patents.