GitHub - WinampDesktop/winamp: Iconic media player
github.com
Iconic media player. Contribute to WinampDesktop/winamp development by creating an account on GitHub.
  • dohpaz42@lemmy.worldEnglish
    831·
    2 months ago

    They are nuts. Their license means that you give up all of your authorship rights to the code you contribute, and on top of that you’re not allowed to distribute modified source, nor can you fork the source for any purpose.

    Edit: lol

    • TachyonTele@lemm.ee
      141·
      2 months ago

      Does that actually matter?
      I’m asking because license stuff is over my head, but I’d like to learn about it more.

          • projectmoon@lemm.ee
            22·
            2 months ago

            Not necessarily. While of course in many many cases, open source is a volunteer effort, there’s usually some implicit transaction going on. Whether that’s improving the software for yourself and passing that on to others, being a business and improving a library or something you use that helps your project generate revenue, or even a straight up commercial transaction.

            But in all these cases, the open source project can be taken by you (or others) and you can do whatever you want with it. In the case of Winamp here, you cannot do any of that. It would be different if they were paying for contributions. But they’re not, so.

            • atzanteol@sh.itjust.worksEnglish
              216·
              2 months ago

              Yeah. You’re talking about 0.0001% of the users though. For everyone else it’s “I don’t want to pay for this”.

      • Kissaki@programming.devEnglish
        14·
        2 months ago

        If you only care about contributing improvements, no, it doesn’t matter.

        If you want to at least be recognized as an author, and be able to say “I made this”, the license opposes that.

        Waiver of Rights: You waive any rights to claim authorship of the contributions […]

        I don’t know how they intend to accept contributions though. I guess code blocks in tickets or patch files? Forking is not allowed, so the typical fork + branch + create a pull request does not work.

        • Amju Wolf@pawb.social
          6·
          2 months ago

          Also, this isn’t even compatible with copyright law in some countries. I.e here you can’t give up authorship at all; you can only grant an irrevocable, perpetual license (that might even prohibit you from distribution yourself and such) but you’ll always be able to say “I made this” no matter what their license says.

      • dohpaz42@lemmy.worldEnglish
        8·
        2 months ago

        The way I look at it is this: I want credit for the work I do, I should also be able to fork a repo that I work on, and I sure as hell don’t like giving up my rights if I can help it.

        But others may feel different.

    • lad@programming.devEnglish
      2·
      2 months ago

      I guess, opening a PR without forking is possible, but hey that’s sort of incredibly bullshit idea

  • AlligatorBlizzard@sh.itjust.works
    18·
    2 months ago

    I love GitHub drama.

    Anyone know if the Dolby code leak is going to lead to anything interesting, or had this code been leaked before? And how fucked are the Winamp folks?

    • sandbox@lemmy.world
      151·
      2 months ago

      You’re acting like releasing the WinAmp source code is like some sort of great gift to open source devs, lol. It’s a community that works based on a set of rules and expectations, if the company doesn’t want to meet those expectations, then an appropriate response is to bully them out of the space (or to bully them into meeting those expectations)

      Projects are not entitled to be received gratefully and respectfully if you treat open source devs like a disposable source of free labour.

      And the concept of “civility” in the face of corporations telling us what we can and can’t do, can well and truly get fucked.

        • pbbananaman@lemmy.world
          62·
          2 months ago

          I don’t think you have a point. You’re shaming people in a community who don’t give a fuck about your concern trolling. Calling out shitty organizations for shitty behavior in the loudest way possible is often the only way to enact change. There’s a distinct power imbalance between companies that have money and resources versus individuals in the open source community. Polite and firm are useless unless you have additional leverage.

        • sandbox@lemmy.world
          41·
          2 months ago

          Right now it looks like a pack of dogs barking around thinking they’re witty and clever for doing so.

          Sure, but that’s pretty much any online community. We’re doing it right now. You did the exact same shit in your original comment where you called the GitHub commenters a bunch of children. We are the dogs in the mirror, if you want to change that culture, be the change.

          Personally, I don’t think that being a smarmy prick in the comments of some corporation GitHub repo is “bad behavior”. It’s definitely not as bad as profiting from the exploitation of unpaid or underpaid labor, anyways.

          When corporations destroy lives, it’s “just business”. But when people refuse to act civilly towards or about corporations, it’s “childish” and “immature”. In that case, I am very proud to be an immature child telling the adults that they’re brainwashed obedient drones complying with the will of then ruling elite.