It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.

  • paperplane@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    3 months ago

    A good reason to pick GPL is if you want to allow GPL software to integrate yours and you don’t care that much about the AGPL clauses (e.g. because your app isn’t a server).

    CC0 might be a good fit for trivial template repos where you don’t want to burden downstream projects with having to include copyright notices.

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

      Absolutely not! Avoid CC0! Stop spreading bad information. If you want a public domain dedication with fallback permissive license the best choice is (sadly) The Unlicense. It is the only public domain dedication with fallback permissive license approved by both FSF and OSI. It’s unfortunate because The Unlicense is still a crayon license.

      If you don’t want to burden some stream projects with including copyright notices, just don’t enforce it if you find people who forgot.

      https://www.gnu.org/licenses/license-list.html#CC0

      If you want to release your non-software work to the public domain, we recommend you use CC0. For works of software it is not recommended, as CC0 has a term expressly stating it does not grant you any patent licenses.

      Because of this lack of patent grant, we encourage you to be careful about using software under this license; you should first consider whether the licensor might want to sue you for patent infringement. If the developer is refusing users patent licenses, the program is in effect a trap for users and users should avoid the program.

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

          If your company won’t let you use MIT licensed software I don’t know what to tell ya. If your company won’t let you use MIT code, which FSF and OSI endorse, but will let you use CC0 code, which FSF and OSI do not endorse, then I really don’t know what to tell ya.

      • paperplane@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        What I mean is that you (IIUC) can’t use an AGPL library in a GPL app without relicensing the whole thing to AGPL. For many larger projects relicensing is a huge hassle and often a non-starter if there aren’t very good reasons for it.