• JohnEdwa@sopuli.xyz
      link
      fedilink
      arrow-up
      12
      ·
      edit-2
      3 days ago

      Bigger problem is the No Derivatives clause of the CC licence, as compiling or forking the code creates a derivative, so it’s now a project nobody is allowed to use (or distribute) in any other form than their exact, precompiled releases.

      In fact, as the GitHub terms of service specifically require you to allow forking - as recently demonstrated by the WinAmp project - I wonder if CC ND is even possible to be used in GitHub in the first place.

      • refalo@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        He claims to have gotten permission from the contributors… not sure where you heard that they didn’t.

      • Chewy@discuss.tchncs.de
        link
        fedilink
        arrow-up
        18
        ·
        3 days ago

        He said somewhere that he did ask a top contributor if they care, and they didn’t. He also said that he rewrote a bunch of code to be able to change the license.

        I can’t verify this, but it doesn’t seem like he infringend on someones copyright. Small changes (e.g. a few lines) don’t even (necessarily) qualify for copyright (just like the few sentences I wrote here likely don’t).

    • toastal@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      To be fair, there are NC software licenses out there under umbrellas like post-open source, copyfair, & copyfarleft. Creative Commons is wrong for this application—& ND is even more questionable—but choosing to follow these other movements is something you can choose to do or support if the noncommercial clause aligns with your philosophy (but incompatibles with GPL & friends can prove difficult).