News for hackers. Stuff that matters.
Re:Winamp Legacy player source code by thomastjeffery on Tuesday September 24, 2024 @11:39AM (#41637736)
You can't blame this one on English.

Before the ambiguity of language can get in the way, there has to be a coherent idea that you want to express in the first place.

This license explicitly contradicts itself. It says you are encouraged to contribute changes to the source, and you may not share changes to the source with anyone ever.

Re:Winamp Legacy player source code by hunter2_ on Tuesday September 24, 2024 @11:52AM (#41637895)
It seems like the intent is to encourage giving changes to exclusively the maintainer, and that forking in this context refers to distribution beyond a private communication between the change proposer and the maintainer.
Re:Winamp Legacy player source code by TeMPOraL on Wednesday September 25, 2024 @03:34AM (#41644690)
Which, this being a git repo, makes perfect sense, as despite the impression GitHub gave to a whole generation of developers, Git was designed with a different contribution workflow in mind: one of sending patches by e-mail. Cloning the repo locally, making changes, formatting a patch, and sending it to the maintainer, seems to be perfectly withing bounds of both intent and text of the license.