this post was submitted on 16 Oct 2024
255 points (100.0% liked)

Open Source

31336 readers
164 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

cross-posted from: https://lemm.ee/post/45026885

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 month ago (2 children)

I'm completely out of the loop. What happened?

[–] Supermariofan67 52 points 1 month ago (2 children)

Winamp published their code as "open source". Problem is...

  1. It wasn't open source, it was proprietary but you can see the source code.
  2. Their custom license didn't even allow forks, which is against GitHub TOS
  3. The codebase apparently contains proprietary code from third parties that they don't have the right to relicense.
  4. The codebase apparently contains GPL code from third parties that they probably didn't have the right to make proprietary in the first place
[–] [email protected] 3 points 1 month ago

On top of that, when told about the proprietary code, they deleted it from the repository thinking that was just the end if it. So they didn't have any idea how git works either.

[–] [email protected] 3 points 1 month ago (1 children)

Wait, there's GPL code there as well???

I'd heard of all the others but this ome kinda snuck under the radar with all the larger issues at play here

[–] Supermariofan67 3 points 1 month ago

The article on theregister stated

Also inside the uploaded source code was some GPL 2 source code, which renders the not-very-open WCL moot.

[–] [email protected] 10 points 1 month ago

Winamp source code was published on github, but the license said you can’t fork or share the code. Such a license isn’t compatible with github, which is all about forking and sharing.