> you agree to allow others to view and "fork" your repositories
How did you come to the conclusion that this does not grant the permissions to fork? It's literally in the sentence. Where else did you find the definition of "forking", if not here? This is what Github defines in the TOS, this is the label on the button in github UI, so clearly this is also what winamp means when they forbid "forking" and that means it's against the TOS. There is no other "forking".
I got it from the TOS:
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).
They explicitly define it as making copies. There is no mention of being allowed to modify said copy. Also note the quotes around "fork", since it differs from the usual definition.
In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software.
(Emphasis mine)
@sweng But what else would "forking" mean? As you said "in the usual sense". This is the usual sense - making a copy of the repo on github = forking.
I edited my reply to include the definition from Wikipedia, but there are of course many other sources.
Look, I can't help you if you don't even read the things you are posting. 🤷♂️
How about you continue reading a bit further, until you hit the word "and".
take a copy of source code from one software package and start independent development
(emphasis mine).
Github defines "forking" as just copying, while normally it is understood as copying + further development (creating a "fork" in the development history, hence the name).
@sweng No need, I can instead continue reading the "license" and see the word "or".
> You may not create, maintain, or distribute
They disallow creating copies. Plus other things, but already creating the fork by either definition is disallowed. Not to mention, wikipedia is not a legal document while the TOS is, the double-quotes are used because that's the first time a new term is used, followed by its definition, and that the license is likely using Github's definition, not wikipedia's
Why on earth would the license use Github's very niche definition? "Forking" as a software concept has been around for decades longer than Github or it's "fork" button has existed.
Also, how about reading the full psragraph?
You may not create, maintain, or distribute a forked version of the software.
(emphasis mine). It only does what you think it does if forking = copying. Which it doesn't.
Question to you: Github provides a button labeled "Download ZIP" for downloading a .zip-file containing the source. If I press that button, am I in your opinion creating a fork?
> Why on earth would the license use Github’s very niche definition?
Maybe because it's ON GITHUB??
Thst's not at all how it works. The definitions made in the TOS do not "leak" out of said TOS (unless the TOS specifies that, which it does not).
@sweng It's much more likely that the term follows the github's definition, because it's on github, rather than the wikipedia's definition, because why would it? You keep hanging on one word in a wikipedia article, let me fix that article and maybe we can stop this nonsense discussion.
@sweng And to your question: I'd say no, downloading as zip is not a fork, either by github TOS (because they say the copy must be in a repo) nor by the license, because they specifically define the term "Modify", and saying that an exact copy is ok, as long as you don't distribute it or "fork" it - which is exactly why "fork" here means the "Fork" button of github.
Do you think that Download ZIP = fork? It sounds to me like it doesn't fit the wikipedia definition either, so what's your point?
So you also agree that copying is not forking as it is commonly understood?
Do you then claim that the license refers ro "fork" as defined in a specific service's TOS (without referencing said servixe at all)?
Otherwise I don't see how you can come to the conclusion that "forking" in the license does not also necessify modification (which is what the common meaning is).
@sweng I simply don't agree that your "common" definition is really the "common" one. Fork is a fork if you created a copy in another repo. Immediately in that moment, even without a new commit. Clearly that's what the "Fork" button does. Not zip, that's not a fork. Nor a private copy, unavailable to anyone else. This fits both the definition from the license, and the TOS, and all instances of "forking" that I've seen before.
makmarian@fedia.io to 
@sweng
> you agree to allow others to view and "fork" your repositories
How did you come to the conclusion that this does not grant the permissions to fork? It's literally in the sentence. Where else did you find the definition of "forking", if not here? This is what Github defines in the TOS, this is the label on the button in github UI, so clearly this is also what winamp means when they forbid "forking" and that means it's against the TOS. There is no other "forking".
I got it from the TOS:
They explicitly define it as making copies. There is no mention of being allowed to modify said copy. Also note the quotes around "fork", since it differs from the usual definition.
E.g. wikpedia (https://en.m.wikipedia.org/wiki/Fork_(software_development) defines it thusly:
(Emphasis mine)
@sweng But what else would "forking" mean? As you said "in the usual sense". This is the usual sense - making a copy of the repo on github = forking.
I edited my reply to include the definition from Wikipedia, but there are of course many other sources.
@sweng
> take a copy of source code
?
@sweng
Look, I can't help you if you don't even read the things you are posting. 🤷♂️
How about you continue reading a bit further, until you hit the word "and".
(emphasis mine).
Github defines "forking" as just copying, while normally it is understood as copying + further development (creating a "fork" in the development history, hence the name).
@sweng No need, I can instead continue reading the "license" and see the word "or".
> You may not create, maintain, or distribute
They disallow creating copies. Plus other things, but already creating the fork by either definition is disallowed. Not to mention, wikipedia is not a legal document while the TOS is, the double-quotes are used because that's the first time a new term is used, followed by its definition, and that the license is likely using Github's definition, not wikipedia's
Why on earth would the license use Github's very niche definition? "Forking" as a software concept has been around for decades longer than Github or it's "fork" button has existed.
Also, how about reading the full psragraph?
(emphasis mine). It only does what you think it does if forking = copying. Which it doesn't.
Question to you: Github provides a button labeled "Download ZIP" for downloading a .zip-file containing the source. If I press that button, am I in your opinion creating a fork?
@sweng
> Why on earth would the license use Github’s very niche definition?
Maybe because it's ON GITHUB??
Thst's not at all how it works. The definitions made in the TOS do not "leak" out of said TOS (unless the TOS specifies that, which it does not).
@sweng It's much more likely that the term follows the github's definition, because it's on github, rather than the wikipedia's definition, because why would it? You keep hanging on one word in a wikipedia article, let me fix that article and maybe we can stop this nonsense discussion.
@sweng And to your question: I'd say no, downloading as zip is not a fork, either by github TOS (because they say the copy must be in a repo) nor by the license, because they specifically define the term "Modify", and saying that an exact copy is ok, as long as you don't distribute it or "fork" it - which is exactly why "fork" here means the "Fork" button of github.
Do you think that Download ZIP = fork? It sounds to me like it doesn't fit the wikipedia definition either, so what's your point?
So you also agree that copying is not forking as it is commonly understood?
Do you then claim that the license refers ro "fork" as defined in a specific service's TOS (without referencing said servixe at all)?
Otherwise I don't see how you can come to the conclusion that "forking" in the license does not also necessify modification (which is what the common meaning is).
@sweng I simply don't agree that your "common" definition is really the "common" one. Fork is a fork if you created a copy in another repo. Immediately in that moment, even without a new commit. Clearly that's what the "Fork" button does. Not zip, that's not a fork. Nor a private copy, unavailable to anyone else. This fits both the definition from the license, and the TOS, and all instances of "forking" that I've seen before.
An article exactly about how Github misuses the word "fork": https://drewdevault.com/2019/05/24/What-is-a-fork.html