?
sweng
joined 1 year ago
I edited my reply to include the definition from Wikipedia, but there are of course many other sources.
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.
E.g. wikpedia (https://en.m.wikipedia.org/wiki/Fork_(software_development) defines it thusly:
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)
The TOS actually does not say you are granting users permissions to fork in the usually understood sense. The TOS gives you permission to copy, which Github calls "forking" even though it isn't.
Just because you can do something, does not mean you are allowed to.
Yes, but that has nothing to do with Github TOS. It does not require you to accept or even allow pull requests.
I feel most people are fundamentally misunderstanding what forking means.
Generally, forking means making a copy and modifying it.
Github, however, seems to define "fork" as just making a copy.
So, in fact there is no "TOS violation". The license forbids making a copy and modifying it, while github requires that you allow making copies. There is no conflict between the two.
Even if it were, just having a license that contradicts the github TOS is not a TOS violation (unless that is separately mentioned somewhere).
You can self-host it, making it as private as you want.
That's the problem with how the app store presents privacy info: without context it's nearly meaningless. "may be collected". It's optional, but that's not show here. The Play store does show that these are all optional.
"Collected" is also a scary word here. Having my location "collected" sounds scary, but what it actually may mean is that I can optionally and explicitly share my location with a contact.
What do you find WTF about it?
As said, that's a truism. What possible reason would one have to say it?
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).