Winamp Legacy player source code

Original Article ↗ Hacker News Discussion ↗

Winamp’s legacy Windows media player source code has been released on GitHub under a new “Winamp Collaborative License,” prompting strong reactions because it allows reading and privately modifying the code but bans forking and distributing modified versions. Commenters argue this makes it “source-available” rather than true open source, conflicts with GitHub’s forking model, and even misuses terms like “copyleft” and “free” in the license text. Alongside nostalgia for Winamp’s influence and curiosity about the old codebase, many conclude the move looks more like a PR and free‑labor play than a genuine handover of control to the community.

Licensing and “Open Source” Controversy

  • The released Winamp Legacy code uses a custom “Winamp Collaborative License” that:
    • Allows viewing and private modification.
    • Explicitly forbids distributing modified versions and “forked” versions.
    • Reserves official distribution to the repository maintainers.
  • Many commenters argue this is “source-available,” not open source or free software by OSI / FSF standards.
  • The license text calls itself “free” and “copyleft,” which several see as misleading or “open washing,” since copyleft normally requires allowing redistribution of modified versions.
  • Some appreciate the source-available middle ground for debugging and learning, even if it’s restrictive.

Forking, GitHub, and Contribution Workflow

  • The “No Forking” clause conflicts with normal GitHub workflows (press Fork, modify, open PR).
  • Confusion exists over whether “fork” means:
    • Any GitHub fork/clone; or
    • A separate long‑term derivative project (e.g., MariaDB vs MySQL).
  • Some suggest contributing only via local patches or email, or GitHub issues with diffs, to stay within the text of the license.
  • Others think the language is internally contradictory: it “encourages” contributions but bans creating modified codebases to test them.

GitHub Terms of Service vs Winamp License

  • GitHub’s ToS states that making a repo public grants other GitHub users the right to view and “fork” it on GitHub.
  • Debate centers on whether this platform right overrides or conflicts with Winamp’s license; suggested outcomes range from “GitHub can enforce only against Winamp” to “users are reasonably protected by ToS.”
  • Many note there are already hundreds of forks despite the prohibition.

Codebase, Dependencies, and Removed Components

  • The code is large and heavily vendor-bundled, including old DirectX SDK pieces and external binaries; some question licensing of these parts.
  • Subsequent commits removed non‑releasable or third‑party code (e.g., Dolby/Fraunhofer, SHOUTcast, GeoIP), but these remain in history and forks.
  • Some remarks on the code as “battle‑worn,” over‑architected in places (Winamp 3 lineage), with entertaining comments and swearing.

Nostalgia, Alternatives, and Community Response

  • Strong nostalgia for Winamp’s UI, stability, and plugin/skin ecosystem; some call it peak audio player design.
  • Others point out existing open‑source clones and alternatives (XMMS, Audacious, qmmp, Foobar, WACUP, etc.).
  • A segment advocates ignoring the project until the license is fixed, seeing it mainly as PR and a bid for free labor under very one‑sided terms.