Winamp Open Source Story Is Over
linuxiac.com
Without warning, Winamp deleted its entire GitHub repository, effectively ending the whole story around open-sourcing the music player code.
    • CosmicTurtle0@lemmy.dbzer0.comEnglish
      52·
      2 months ago

      They wanted free labor but own the changes.

      They could have gotten free labor if they used a standard license like GPL or even MIT.

      But nope. They were greedy.

  • Hamartiogonic@sopuli.xyz
    40·
    2 months ago

    LOL. Those 3 weeks must have been really exciting at Llama Group. I can only imagine how the conversion went when the engineers tried to explain what FOSS means and the CEO understood none of it.

  • 1984@lemmy.today
    221·
    2 months ago

    I don’t even understand why anyone cares about winamp anymore. Or how the company figured people should be happy to work for free on it without it being open source.

    • BeN9o@lemmy.worldEnglish
      1·
      2 months ago

      I don’t understand why anyone cares about winamp being updated, I still use winamp, have my music library locally and it does exactly what I need it to… play music. What are winamp even trying to do at this point, take over streaming?

  • fulg@lemmy.world
    11·
    2 months ago

    I thought I read elsewhere there were some GPL 2 parts in there too, I guess not.

    I tried to find a source for this more credible than “I remember reading it on Lemmy” but couldn’t, now that the repo is deleted nobody can confirm. Perhaps some forks still exist… 🤔

    • lad@programming.devEnglish
      11·
      2 months ago

      Perhaps some forks still exist…

      No, that’s impossible, because they didn’t allow it 😭

      • Scoopta@programming.dev
        5·
        2 months ago

        According to the article they did allow it. They got rid of that clause in a license update, just didn’t allow you to modify your fork lol

  • Kissaki@programming.devEnglish
    1·
    2 months ago

    I wasn’t aware the GitHub terms of service explicitly grant / require you to grant permission to fork [within GitHub].

    GitHub ToS section License Grant to Other Users

    By setting your repositories to be viewed publicly, you agree to allow others to view and “fork” your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).

    If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub’s functionality (for example, through forking). […] If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.