this post was submitted on 24 Sep 2024
140 points (99.3% liked)
Open Source
31378 readers
178 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@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
An article exactly about how Github misuses the word "fork": https://drewdevault.com/2019/05/24/What-is-a-fork.html
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 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.
Tying "fork" to "repositories" is nonsense, because software forks have existed longer thsn e.g. git.
How do you define "repository", such that it makes sense? Is it only Git repositories? Any version control system? How about a .zip-file placed on an FTP server?
@sweng Look I don't have that much time to split hairs about inconsequential things. All I'm saying is that if someone says "Don't do ABCD" and you click a button on the same page that says "Do ABCD" then that's clearly the same ABCD they were talking about, no more action necessary, no outside definitions necessary. Have a good day.
The point is, it's not at all clear, because Github has it's own definition of what "fork" means. I'm honestly not sure why it's so hard to grasp.
@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.
Can you fix dictionary.com as well?
https://www.dictionary.com/browse/fork