News for hackers. Stuff that matters.
Re:Winamp Legacy player source code by maxerickson on Tuesday September 24, 2024 @01:30PM (#41638924)
Any public GitHub fork is being distributed.
Re:Winamp Legacy player source code by swinglock on Tuesday September 24, 2024 @02:15PM (#41639398)
Is forking a well defined term? Doubt it will hold up in court.
Re:Winamp Legacy player source code by maxerickson on Tuesday September 24, 2024 @04:46PM (#41640740)
They don't give permission, so the lack of definition doesn't really matter.

If they were trying to grant a narrow permission and then enjoin someone they thought was outside of their definition, it would matter (But they just aren't giving permission to distribute modified versions).

Re:Winamp Legacy player source code by willcipriano on Tuesday September 24, 2024 @03:17PM (#41639918)
Anything the owners of the Winamp code can find in order to take legal action on will be distributed. Rule 2 (and 3) is always superfluous in practice.
Re:Winamp Legacy player source code by efilife on Tuesday September 24, 2024 @01:55PM (#41639168)
You can't have a private Github fork
Re:Winamp Legacy player source code by bdcravens on Tuesday September 24, 2024 @02:15PM (#41639400)
Yes you can; it's set at the organization level

https://docs.github.com/en/organizations/managing-organizati...

Re:Winamp Legacy player source code by efilife on Tuesday September 24, 2024 @04:16PM (#41640456)
I stand corrected
Re:Winamp Legacy player source code by zorgmonkey on Tuesday September 24, 2024 @02:35PM (#41639582)
You can, but only private forks of a private repo are allowed. Private forks of public repos are not allowed by design (modulo some weird bugs that were discussed on a past post).