321–330 of 345 posts
...
750Mb later: WTF?
[tippety tappety clickedy clackedy]
Oh.... they vendored everything, including a bunch of external x86 binaries. 32- and 64-bit. FFS.
But also - I sure hope they got the licensing correct for those parts...
The best thing we can do for the future of the project is to NOT engage with the project at this time ... Even just cloning the project into your private workspace to review / compile is giving more engagement than their current licensing stance warrants. I'll check again when an HN post comes out stating they've changed their licensing stance - Until then, closing this tab and forgetting about it ...
The author justin frankel (also wrote reaper the DAW absolute legend) had this to say about it > Question: Now that WinAMP's source has been officially released, do you have any desire to hack new badass features in? Answer: If I did have any desire, it would be extinguished by the license terms, lol. The terms are completely absurd in the way they are written, e.g. "You may not create, maintain, or distribute a fork…
Earlier quoted context omitted.
The author justin frankel (also wrote reaper the DAW absolute legend) had this to say about it > Question: Now that WinAMP's source has been officially released, do you have any desire to hack new badass features in? Answer: If I did have any desire, it would be extinguished by the license terms, lol. The terms are completely absurd in the way they are written, e.g. "You may not create, maintain, or distribute a fork…
where is this quote from?
Earlier quoted context omitted.
The legal system don't work that way. That ToS is between wimamp and GitHub, not you. You have to do the due diligence to get the permission from winamp. You might be able to get away by suing GitHub and have them sue winamp. ..
https://www.law.cornell.edu/wex/third-party_beneficiary
Earlier quoted context omitted.
It's not clear that Github's ToS can do such a thing, is it? What gives them the right to overrule the license from Winamp to me?
Because Winamp agreed to the ToS of GitHub by uploading their code to GitHub.
Earlier quoted context omitted.
It's not clear that Github's ToS can do such a thing, is it? What gives them the right to overrule the license from Winamp to me?
A repo's license doesn't overrule GitHub's policy.
Earlier quoted context omitted.
Because Winamp agreed to the ToS of GitHub by uploading their code to GitHub.
The legal system don't work that way. That ToS is between wimamp and GitHub, not you. You have to do the due diligence to get the permission from winamp. You might be able to get away by suing GitHub and have them sue winamp. ..
I'm curious how they expect people to contribute to the project. Section 4 of the license says "Contribution to Project: You are encouraged to contribute improvements, enhancements, and bug fixes back to the project. Contributions must be submitted to the official repository and will be reviewed and incorporated at the discretion of the maintainers." However, the restrictions in Section 5 ban forking the code or dist…
The Github ToS gives users the right to fork any public repos.