140
submitted 6 days ago by makmarian@fedia.io to c/opensource@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] chebra@mstdn.io 1 points 6 days ago

@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.

[-] sweng@programming.dev 0 points 6 days ago

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?

[-] chebra@mstdn.io 1 points 6 days ago

@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.

[-] sweng@programming.dev 0 points 5 days ago

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.

this post was submitted on 24 Sep 2024
140 points (99.3% liked)

Open Source

30511 readers
177 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS