search

WinampDesktop / winamp

Iconic media player
https://winamp.com
Other
7.61k stars 1.8k forks source link

Delete this mess #258

Open MichaelAgarkov opened 1 day ago

MichaelAgarkov commented 1 day ago

The Winamp source code on GitHub doesn't only violate GitHub TOS, but also violates the LGPL, contains code copyrighted by Frauhofer and Dolby, but the copyright waiver is also illegal in many countries. The license agreement calls itself copyleft when it's absolutely not. You are de facto not allowed to fork the repository, but allowed to make commits, but can't do that without forking. It's an absolute mess.

giantplaceholder commented 1 day ago

I second this. In its current form, the legal status of this repo's code is dubious at best.

Large projects like this typically go through a clean-up process to ensure that no third-party software, which cannot be made publicly available, makes its way to the end user. For instance, this is what was done with all open-source releases of the id Tech engine back when Carmack was in charge.

In the last 24 hours, there have been several instances of proprietary code, leftover artifacts, and improperly licensed GPL/LGPL code found in the project.

The best course of action would be to make this repo private, clean it up, and thoroughly review the contents and licensing before making it public again.

This situation is already as complicated as it can be. It's time for damage control.

LokiFawkes commented 1 day ago

Winamp won't listen. But if you really wanna whip the llama's ass, open an issue on my fork describing the instances of improperly licensed code, and I'll see if I can rectify it in my version. Don't want to un-copyleft any foss code they've stolen, after all.

LokiFawkes commented 1 day ago

Some reason GH disabled issues on my fork. Re-enabled it now.

mechabubba commented 1 day ago

In the last 24 hours, there have been several instances of proprietary code, leftover artifacts, and improperly licensed GPL/LGPL code found in the project.

this is striking to me. more and more copyrighted code keeps being found in the repo. from the original announcement, they had four months to get this right. seriously, did they do any preparation before uploading this? apart from that free labor license.

start over. do it properly. delete the repo and actually prepare properly before doing this.

LokiFawkes commented 1 day ago

After doing some digging, I found it unconscionable to maintain a fork of this, even to stick it to the llama. Wait for the lawsuits to roll in, this shit is doomed.