News for hackers. Stuff that matters.
Re:Winamp Legacy player source code by kube-system on Tuesday September 24, 2024 @11:20AM (#41637490)
The GitHub ToS is not a software license. It is the terms for using the GitHub service. The penalty for breaking it is that your GitHub services might be terminated, not that they can somehow relicense your software.
Re:Winamp Legacy player source code by trehalose on Tuesday September 24, 2024 @11:29AM (#41637599)
This part of the ToS explicitly does grant such a license to other GitHub users.

> If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking).

Re:Winamp Legacy player source code by IgorPartola on Tuesday September 24, 2024 @12:11PM (#41638104)
As written, this says that you can fork a repo but can’t then clone it and work on it on your own machine. Isn’t software licensing fun?
Re:Winamp Legacy player source code by skeaker on Tuesday September 24, 2024 @01:25PM (#41638856)
Interesting. I guess you could just stick to the Github web editor to stay compliant? Really a terrible way to go about things though
Re:Winamp Legacy player source code by IgorPartola on Tuesday September 24, 2024 @02:06PM (#41639300)
You also can’t run the code.
Re:Winamp Legacy player source code by bee_rider on Tuesday September 24, 2024 @02:15PM (#41639396)
Hmm, it says not to distribute the source or the binary. What about WASM or LLVM IR?
Re:Winamp Legacy player source code by IgorPartola on Tuesday September 24, 2024 @02:45PM (#41639664)
If GH provides they capability I suppose.
Re:Winamp Legacy player source code by trehalose on Tuesday September 24, 2024 @04:22PM (#41640510)
I was thinking that. The language seems not quite clear, at least to a non-lawyer like me:

> you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking)

So, on GitHub, we can "use", "perform", and "reproduce". Does editing/modifying fall under any of those verbs?

Re:Winamp Legacy player source code by SixtyHurtz on Tuesday September 24, 2024 @04:33PM (#41640625)
Cloning is part of GitHub's functionality, so therefore we can clone it but can only commit those changes back to GH. We are permitted to do anything that is part of GH's functionality.
Re:Winamp Legacy player source code by efilife on Tuesday September 24, 2024 @11:47AM (#41637835)
It would seem that Github's TOS is superior to their license. They could have chosen other way to host their code