Winamp Legacy player source code is now open

CommunityNews · 24 September 2024 15:01

GitHub - WinampDesktop/winamp: Iconic media player.
Iconic media player. Contribute to WinampDesktop/winamp development by creating an account on GitHub.

Read in full here:

This thread was posted by one of our members via one of our news source trackers.

jmagnani · 25 September 2024 06:56

Used this software a lot during my college days

Eiji · 30 September 2024 01:48

Excellent news! Honestly one of best news recently. Winamp for many people is a player that was used even in childhood. I remember many players used it’s skins even on old mobile phones (not smartphones). Seeing it open now is just amazing!

Edit: Oh, did you saw that repository? It’s completely mess. Their license looks like generated by AI, they violates GitHub’s Terms of Service and Open Source Principles, see:

github.com/WinampDesktop/winamp

Winamp Collaborative License (WCL) Violates GitHub Terms of Service and Open Source Principles

opened 10:45AM - 29 Sep 24 UTC

SoftwareRat

The Winamp Collaborative License (WCL) Version 1.0.1 currently used for this rep…ository violates GitHub's Terms of Service and contradicts fundamental open source principles. Here are the key issues: 1. Violation of GitHub ToS: GitHub's Terms of Service state: "By setting your repositories to be viewed publicly, you agree to allow others to view and fork your repositories." The WCL explicitly prohibits forking and distribution of modified versions, which directly conflicts with this requirement. 2. Not Open Source: The license fails to meet the Open Source Definition as outlined by the Open Source Initiative. Specifically: - It restricts redistribution (Section 5) - It does not allow modifications to be distributed (Section 5) - It requires all contributions to assign rights to Winamp (Section 4) 3. Restrictive Contribution Terms: The license requires contributors to waive their rights and assign all intellectual property to Winamp without compensation (Section 4). This is highly unusual and potentially unenforceable in many jurisdictions. 4. No Forking Allowed: Section 5 prohibits the distribution of modified versions, which is a fundamental right in open source software. This severely limits collaboration and community involvement. 5. Trademark Restrictions: While protecting trademarks is understandable, the license's approach is overly restrictive and incompatible with open source practices. Recommendations: 1. Adopt a standard open source license (e.g., GPL, MIT, Apache) that complies with GitHub ToS and open source principles. 2. If trademark protection is a concern, implement it separately from the software license. 3. Remove the rights assignment clause for contributions or make it optional. 4. Allow forking and distribution of modified versions, with clear guidelines on branding/trademark usage. This license, as it stands, is neither open source nor compliant with GitHub's policies. It should be revised to align with established open source practices and GitHub's requirements.

Also the issues created by trolls. I have no idea what would be the future of it.

jss · 1 October 2024 01:36

I saw on twitter people complaining that you are not even allowed fork the repo. Is this still true?

Eiji · 1 October 2024 04:27

It was true, but this part was removed. It’s still far away from good - for some reason they try to force their own license even if they can’t write it on their own. They need to have extreme costs cuts as they were or still are using ChatGPT for some or all of the work. It’s fail of the year, but let’s give them some time and we would see in what direction it goes …

jss · 6 October 2024 21:07

I agree. Thanks.

Eiji · 7 October 2024 02:02

In this video it’s described what exactly gone wrong:

KnowledgeIsPower · 7 October 2024 14:20

In the issues section

There are all sorts of comments (some comments are not the type that we usually anticipated for GitHub style)