This is "done", subject to the bugs that are in the tracker.

Yay palhmbs and Mark and everyone else that pushed this forward.

The "Final Git Changes" patch missed 0.11.04 by about 3 minutes, but it's still
April somewhere in the world.

Hopefully the new changes to add some <code> tags to make the git commands clearer 
works in this patch.

I've decided to use <abrev> to include some hints - and I put paulproteus's note 
at the bottom of "Creating a Patch" 

I decided to link to the diff patch mission from inside that note, and the 
settings.py has the http:// instead of git://

Hopefully I've managed to add in paulproteus's suggestions...

Please review!

Seems that Travis has disappeared. Therefore, I'll finish this off for this 
milestone.

I've been trying to work out how to pass http through nginx, so that git clone 
works. So far I haven't found a solution. 
Also, most people nowadays are using gitolite to serve up their repos, and I'm 
pretty sure we don't need as complete as gitolite.

paulproteus thought it would be easy using -- 
http://norbu09.org/2009/08/02/git-via-HTTP-(startup-automation-3).html

I have tried with directions above and -- 
http://www.toofishes.net/blog/git-smart-http-transport-nginx/

I also have gone through the mission and it all seems to work wonderfully with a 
git daemon on git://.

Fixed a small problem with a URL - was a return between url and mysite

  -<p>If you want to know more about git, read <a href="{% url
  -mysite.missions.git.views.long_description %}">more about Git</a>.</p>
  +<p>If you want to know more about git, read
  +<a href="{% url mysite.missions.git.views.long_description %}">more about 
Git</a>.</p>

This patch actually applies, and isn't corrupted by cgit.

Here be a squashed version of Mark's patch, after fixing tht mysite/settings.py
diffs to apply on the current origin/master.

Me and TravisB are gonna work on this for the milestone - so I added Travisb to 
the nosy.

Attached is the patch of everything I have thus far. Additional changes needed is 
the feedback from paulproteus and the ability to serve the repository.  The URL 
for checkout will need to be updated in the template, as it currently says to use 
the git method of pulling the repo, rather than http.

Feedback from paulproteus. (note it was later decided that a specific bash/editor 
mission was probably more suited to teaching those skills than the git mission 
would be.)

* Second page: You're asking people to read the code comments to find the author 
of something, but that's confusing because "git log" and "git annotate" (AKA "git 
blame") are the more common tools for finding the author of some code. Maybe you 
could ask them to do something different, like paste the output of the program?

Also, people have suggested we explain to people they need to "cd" into a 
directory, or open a particular file with a text editor -- whatever you ask 
people to do, it should only be unclear if that's what you want. We can't 
necessarily assume much of the skill level of people running through these 
missions.

* Third page: I would link to the diff/patch mission in the text, and also have a 
paragraph like:

"Files created by git format-patch are like normal patch files, but they also 
carry information about the git commit that created the patch: the author, the 
date, and the commit log message are all there at the top of the patch."

Also, you don't explain here how to "check your changes into your local copy".

Also, if the person is an OS X user, we could suggest they creating the
patch with GitX, or with gitg in GNU/Linux-y systems.

Also, "open the patch file" in what?

A snapshot of Mark's work so far is at 
https://docs.google.com/document/d/16uZQWvvYWoWob2gjwCwqv24Wi9IRfllqCb5pw0oiu9c
/edit?hl=en&authkey=CP2JvrIM

Mark just posted on Devel that he is getting close to having patches for this,
so I'm chucking it in the latest milestone (which we now have two weeks for ^_^ ).

Notes from Paulproteus: the most useful one would be a training mission that 
teaches how to use git format-patch, assuming no git knowledge.

This month's milestone is turning out to be too ambitious :(

Hey Mike!

I think that it would be helpful to agree on the "plot" of the mission before
you start coding it. If you have some ideas for it, I suggest you mail them to
devel@ and we can discuss there. If  not, then you and I and the rest of
#openhatch can brainstorrm on IRC first.

Then, I suggest that you submit some patches that add the skeleton of the
mission to the codebase. By "skeleton" I'm thinking, just enough to show all the
pages, and put some placeholder text on them.

Then, I suggest you modify the mission so it actually does whatever the "meat"
of the mission is. (For example, for the Subversion mission, this would be
tracking the state of the user through the mission, and the work of creating a
Subversion repository for the user, and the complex code that validates the
user's input.)

I've started this just now...

Later!

It would be really nice if we had a training mission for "git". Then we could
remove the "First, a word about git" discussion from
http://openhatch.org/wiki/Adding_a_field_to_the_profile