Earlier quoted context omitted.
Any public GitHub fork is being distributed.
You can't have a private Github fork
Yes you can; it's set at the organization level
https://docs.github.com/en/organizations/managing-organizati...
Winamp Legacy player source code
201–210 of 345 posts
Re: Winamp Legacy player source code
#202Open sourcing is always good, because maybe you can learn some things by reading it. Also, Winamp Legacy is a fairly important piece of software, so having an archive of its source is a great thing. But the restrictions on the source are interesting. To quote the license file: * No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form. * No Forki…
This seems to go against GitHub's own ToS[1]: > By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). [1] https://docs.github.com/en/site-policy/github-terms/github-t...
You can fork it but not commit to it? LOL
Re: Winamp Legacy player source code
#203man, at first glance doesnt look like a lot of work to add support to linux.
Care to elaborate on how you can see that? Eager to learn
Re: Winamp Legacy player source code
#204If you want a free copy of the SHOUTcast server software, they illegally share that code in their repo ..
Here it is from a snapshot before removal:
https://github.com/WinampDesktop/winamp/tree/3ab19235a69d96b...
Re: Winamp Legacy player source code
#205Earlier quoted context omitted.
What is the other meaning of fork? When you click "fork this repo" in GitHub, that clones the repository, and re-publishes it under your username. When you clone a repo to your system privately, that does not involve publishing. If this is their intended meaning of "fork", then this license must explicitly disallow cloning the repo!
> What is the other meaning of fork? The older, still in use today meaning is what happened when Oracle bought MySQL and ruined it. People forked it and now we have MariaDB. Basically, it means a fork in the code base and now there are two separate projects.
OK, but that's still not different.
When you fork a project on GitHub, that literally creates a parallel working history, and publishes it under your username. That's what GitHub means by "fork".
So what's the other definition?
Re: Winamp Legacy player source code
#206Earlier quoted context omitted.
> What is the other meaning of fork? The older, still in use today meaning is what happened when Oracle bought MySQL and ruined it. People forked it and now we have MariaDB. Basically, it means a fork in the code base and now there are two separate projects.
OK, but that's still not different. When you fork a project on GitHub, that literally creates a parallel working history, and publishes it under your username. That's what GitHub means by "fork". So what's the other definition?
Many years ago I would have called that "mirroring", which is definitely not forking.
Re: Winamp Legacy player source code
#207The only music player that wasn't annoying. Just did its job with a streamlined interface, without the clutter and clunky graphics that competitors thought was the way to go.
Re: Winamp Legacy player source code
#208Earlier quoted context omitted.
You can't have a private Github fork
Yes you can; it's set at the organization level https://docs.github.com/en/organizations/managing-organizati...
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).
Re: Winamp Legacy player source code
#209Earlier quoted context omitted.
Here you go https://about.winamp.com/press/article/winamp-open-source-co...
Thanks for sharing. Wonder if they've ever heard of color contrast. Dark blue on dark blue is not very readable. Had to highlight the article to read it.
Coincidentally, I thought it was this bug that bit you; it was reported a couple of days ago https://github.com/mui/material-ui/issues/43823
Re: Winamp Legacy player source code
#210Bizarre license reeks of a company that doesn't know what to do with their own highly regarded software but is desperate for the community to give them free improvements that they can later monetize.