Winamp owner Llama Group deletes the GitHub repository of the legacy player's source code posted on September 24, following criticism on the way it was released
Winamp, through its Belgian owner Llama Group, posted the source for its “Legacy Player Code” on September 24 so that developers could …
Ars TechnicaKevin Purdy
Context & Ripple Effects
Llama Group first made Winamp’s legacy-player code available to developers, then reversed course after objections to its release approach. That makes the episode less about a new player feature than about the conditions under which a legacy codebase can be reused.
Developers lose the repository as an official source for inspecting, building on, or contributing to Winamp’s legacy-player code.
Llama Group must resolve the release criticism before any renewed developer-facing distribution can carry clear expectations around access and reuse.
Second-order effects
Potential contributors and projects considering compatibility work will likely wait for a clarified release path rather than treating the withdrawn repository as a stable dependency.
The reversal reinforces the value of explicit repository governance: GitHub-hosted code can be publicly visible yet still subject to rapid removal or altered access terms.
Third-order effects
If more companies expose legacy code without settled licensing and contribution rules, open-source-style releases may increasingly be judged by their governance and durability, not simply by whether code was posted.
The episode points to a continuing split between code publication as a community-development commitment and publication as a controlled corporate asset; which model prevails depends on how owners define reuse rights upfront.
The trend: Legacy software owners are testing developer-facing code releases while tightening control over licensing, stewardship, and the permanence of public repositories.
Have I ever mentioned that software licenses matter? 😅 If you saw the bizarro license that Winamp released their code under, it's now totally gone - as in the code. Including others' code, under your bizarro license is not a good idea. https://arstechnica.com/...
“...It does serve as an example, both of how not to do this sort of thing, but also and more sadly, of why most companies tend not to do so.” #winamp #opensource https://www.theregister.com/ ...
@LundukeJournal ... It's easy, they accidentally published commercial source code to git without understanding how that works or how GitHub itself works for that matter. The best response is to pull the entire thing, then upload what they do own, assuming they come back at all.
Following criticism for the way it released the source code for Winamp under a very restrictive license, Llama Group has deleted the GitHub repository. It looks like the license was just one of many problems. https://arstechnica.com/...
I don't understand what all the fuss is about. Winamp's license is a source-available variant of a strong copyleft license — so strong, in fact, that it's also a codified single-source license. Nothing wrong with that, imo, given we allow “copyleft” to be divorced from OSS/FSF.
Anyone seen the insanity that's going on with Winamp ATM? Winamp was sold off & promised to open source, one problem, they didn't clean up the source code! It leaks the source code for multiple codecs inc. Dolby, a bunch of obscure formats & DEV ACCESS TO MICROSOFTS DEV PORTAL!