Too late the code is out there ... Forever
this post was submitted on 16 Oct 2024
235 points (99.6% liked)
Open Source
30764 readers
1038 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
ohhh nooooo, who could possibly have seen this coming
not like that repo was getting constantly vandalized as people realized it contained copyrighted code that the winamp owners didn't have the rights to which the project managers were halfheartedly playing whack-a-mole with
I know, right... Damn foss enthusiasts, you show 'em sources in order to get some cheap publicity, and those bastards immediately start raising a stink over you slightly attempting to fuck them over with licensing
Llamas ass, only slightly ~~fucked over~~ whipped.
I mean they don't understand SW, Licenses and Git. It's all out there now...
Hey at least we got some commercial secrets and licenses. It's always nice to get those.
Stashing it on the shelf next to my copy of the Windows 2000 source code...
Is art.
Not that pretty.
Did they comment on why it was deleted? I didn't see anything in the article. I recall the consensus was that they made so many mistakes the only way to fix it was deletion of the repo.
I also saw in one of the comments of the Arstechnica article that the one who pushed for open-source wanted to clean up the code before publishing. Management said no, the entire team got fired/left, and suddenly the code got published with all that commercial stuff left in. Sounds about right.
Based on the article, this is a train wreck of cosmic proportions. My guess is, the CEO panicked and went into damage mitigation mode.
Sounds like they’re trying to put out a titanium fire using only a bucket of water. What could go wrong.
Sounds like they’re trying to put out a titanium fire using only a bucket of water.
I have a new phrase to use in the future.
I must say, this whole shitshow has been pretty funny to watch :)
Sometimes the real value of a project isn't its proposed worth, but the schadenfreude it offers instead. I've backed a few failed Kickstarters that I absolutely got my money's worth on.
I'm completely out of the loop. What happened?
Winamp published their code as "open source". Problem is...
- It wasn't open source, it was proprietary but you can see the source code.
- Their custom license didn't even allow forks, which is against GitHub TOS
- The codebase apparently contains proprietary code from third parties that they don't have the right to relicense.
- The codebase apparently contains GPL code from third parties that they probably didn't have the right to make proprietary in the first place
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
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.
Is this what whipping the llamas ass looks like?