• spartanatreyu@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    4 months ago
    1. Any dev can fork it and do the work themselves Edit: Project is licenced to disallow forks (but that wouldn’t stop the community from supporting linux builds, see my comment further down the chain)
    2. Community forks can exacerbate rather than fix the problem, see the Fedora OBS fiasco (link: https://www.youtube.com/watch?v=dJJvq3dpylM)
    • BaroqueInMind@piefed.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      4 months ago

      I don’t know if you missed the comment referring to it, but the dev deliberately changed the license to his source code to prevent forks, so I was being sarcastic, and the dev is indeed being a stupid dipshit suffering from the consequences of their own actions.

      • spartanatreyu@programming.dev
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        the dev deliberately changed the license to his source code to prevent forks

        The licence is a creative commons licence and hasn’t been changed in 11 months.

        I’m not sure what you’re talking about

          • spartanatreyu@programming.dev
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 months ago

            Looks like you can’t distribute a modified version of the project (e.g. a fork), but it wouldn’t stop anyone contributing to or distributing a separate project that users could run locally to patch duckstation’s build process where they can now build it on and for their own machines.

            A build patch wouldn’t contain any copyrighted material, so anyone could contribute and distribute it.

            Ironic considering that’s how many emulator get around legal issues. Emulators distribute virtual machines, but they don’t distribute the copyrighted material.