Review these two week 5 PDFs and comment

[akallish]

Branching_Assignment.pdf
Branching_Overview.pdf

[Tombodil]

Branching Overview
Overall great and the language is a lot tighter then the prelim version. One inaccuracy though...
" When a branch is created, in the GitHub code tab, two files are automatically created :
a general license file and a readme file. "
This is incorrect in that when a branch is created its similar to creating a file folder on a computer. It creates a new location but nothing is created inherently. When you save a file into a new branch your actually completing two different actions: you are creating a new branch (1) and then you are saving an edited copy of a source file within the new branch (2).
Other then that it's pretty good. However you are talking about commits and technically you're talking about commits and pushes. Commits are whn you've made edits and wish to stage those files for upload (pushing) to the branch you've made or had made prior. For the sake of the class this shouldn't be much an issue.
Otherwise it's good.

The assignment will need a bit of cleaning up. There's a mix of 'fork' and 'branch' while the language suggests the product managers will create all the branches before any team members make any edits. May be important to have each team member go through the process of creating their own branch so they have the experience and the PM's will have to check to see new branches having been completed prior to them recieving any given pull request.

I'm going to make a copy of it on the wiki and then make some edits. Will be done by tomorrow evening so we can catch up changes from this week and see where we're at.

[akallish]

Hey Tom:

We discussed that forking and branching are not interchangeable, even though the sort of do the same thing. As I understand it, forking is when you create a fork on a local drive and do not intend to share it. A branch is created in order to iterate and share. I may be wrong . . .

How about this:

When a branch is created its similar to creating a file folder on a computer. It creates a new location for experiments, but nothing is created in the branch. When any file is saved into a new branch, two different actions happen :

(1) you are creating a new branch
(2) you are saving an edited copy of a source file within the new branch

You can create as many source files as needed and are within the folder. The source files are modified through "commits." When enough edits have been made and you are ready to submit the final iteration, the source file is staged for upload (pushing) to the branch you've made.

The question I have is:

1. Does the product manager make all the master source files and then these are branched by each student
2. Each student makes a branch and the product manager make all the master source files and pushes it to each branch