4 ms·

Why does that audience need to know what fork and pull are? It isn't really useful information to them. Knowing that Github is a place to store versions of code

Why does that audience need to know what fork and pull are? It isn't really useful information to them. Knowing that Github is a place to store versions of code might be useful because the name is batted around a lot, but the average non-technical human doesn't really need to know what forking is. Here is my try: Repository: a library of computer codes Forked: when you copy one of the books in the library, make changes to it, and put it back in the library Pull Request: asking the owner of the book in the library to combine your forked, edited book, back into their main copy

aestra 13y ago
The average non-technical person doesn't know what code is, or that code is versioned. Telling them Github stores code isn't very useful without first telling them what code is. I'm going to say at least 50% of people don't even have a conceptual understanding of what software even is. I've learned this from having conversations with various people. Relating it to library books is interesting...
- gjmulhol 13y ago
  Agree. Maybe calling them "computer programs" makes more sense. Just from the frame in the picture, it appears that they are just trying to decribe to their viewers why Github has such a high valuation. To answer that question, they probably should just say something like: "Github is a web company that allows programmers to collaborate on writing new software." When it comes down to it, all versioning systems basically enable 2 things: 1. Versioning 2. User tracking I think you are right about the first one, versioning is a very simple idea but difficult to communicate in a Fox sidebar, so when talking about the core value delivered by Github to a layman, it is that many people can edit code in a controllable way. The reason I say programmers and not developers is that I think developers is another word that the majority of society might get hung up on.
phaemon 13y ago
I'm not a big fan of analogies when they're not necessary. I'd go with something simpler like: * Repository: An online folder containing computer code * Forked: When a repository is copied, so you can edit it * Pull request: A request for the edits you've made to your copy, be "pulled" into the original
- simonlang 13y ago
  by far the best explanation I've read in this thread
- aestra 13y ago
  I don't know why one would define "forked" rather than "fork." * Fork: A copy of a repository. It is copied it can be edited independently.
  - phaemon 13y ago
    I don't know why they would define any of them - it's nothing to do with the story at all, but I thought I should stick with the ones they chose. Well, actually, I can guess why: "repository" sounds a bit like "suppository", and "forked" and "pull request" sound vaguely sexual. It's the kind of thing that would appeal to some people as being a bit risqué. sigh

aestra 13y ago

The average non-technical person doesn't know what code is, or that code is versioned. Telling them Github stores code isn't very useful without first telling them what code is. I'm going to say at least 50% of people don't even have a conceptual understanding of what software even is. I've learned this from having conversations with various people. Relating it to library books is interesting...

gjmulhol 13y ago
Agree. Maybe calling them "computer programs" makes more sense. Just from the frame in the picture, it appears that they are just trying to decribe to their viewers why Github has such a high valuation. To answer that question, they probably should just say something like: "Github is a web company that allows programmers to collaborate on writing new software." When it comes down to it, all versioning systems basically enable 2 things: 1. Versioning 2. User tracking I think you are right about the first one, versioning is a very simple idea but difficult to communicate in a Fox sidebar, so when talking about the core value delivered by Github to a layman, it is that many people can edit code in a controllable way. The reason I say programmers and not developers is that I think developers is another word that the majority of society might get hung up on.

phaemon 13y ago

I'm not a big fan of analogies when they're not necessary. I'd go with something simpler like: * Repository: An online folder containing computer code * Forked: When a repository is copied, so you can edit it * Pull request: A request for the edits you've made to your copy, be "pulled" into the original

simonlang 13y ago
by far the best explanation I've read in this thread
aestra 13y ago
I don't know why one would define "forked" rather than "fork." * Fork: A copy of a repository. It is copied it can be edited independently.
- phaemon 13y ago
  I don't know why they would define any of them - it's nothing to do with the story at all, but I thought I should stick with the ones they chose. Well, actually, I can guess why: "repository" sounds a bit like "suppository", and "forked" and "pull request" sound vaguely sexual. It's the kind of thing that would appeal to some people as being a bit risqué. sigh