[Devel] Update on git mission!

[Mark Freeman]

Sure.  This one could be a little tricky.  With the other missions,
the input back from the user is expected to be something specific.
How would you do that with bash...?

On Sat, Apr 16, 2011 at 9:09 PM, Paul Bakulich <paulbakulich at gmail.com> wrote:
> Hi Mark,
>
> I'd appreciate if you could help flesh out a plot for the "Bash mission".
>
> Paul
>
> On 17/04/2011, Jack Grigg <me at jackgrigg.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> That tracker entry was a result of today's meeting. And yes, I agree - I
>> would recommend this "basic bash" mission to be a "prerequisite" of
>> sorts for all of them, or at least have the other missions like Tar etc.
>> linking in the relevant places to it.
>>
>> Jack
>>
>> On 17/04/11 01:48, Mark Freeman wrote:
>>> I noticed this tracker entry by Paul.  What if we saved the lessons on
>>> using the Unix Shell and such for a dedicated mission? It seems to
>>> make more sense to me to do that, versus trying to bolt it on to the
>>> Git training mission that I am currently working on. See below:
>>>
>>> New submission from palhmbs <paulbakulich at gmail.com>:
>>>
>>> We really need to teach people basic bash skills.
>>>
>>> Let's create an awesome mission to teach:
>>>
>>> * Linux filesystem
>>> * Grep
>>> * Vi / Vim basics
>>> * & your comments / additions totally appreciated.
>>>
>>> Paul
>>>
>>> ----------
>>> assignedto: palhmbs
>>> messages: 1556
>>> milestone: 0.11.04
>>> nosy: palhmbs, paulproteus
>>> priority: feature
>>> status: chatting
>>> title: Create new "Git Mission" for Terminal (cli/bash) skills
>>>
>>> On Fri, Apr 15, 2011 at 5:03 PM, Asheesh Laroia <asheesh at asheesh.org>
>>> wrote:
>>>> On Thu, 14 Apr 2011, Mark Freeman wrote:
>>>>
>>>>> I don't have a publicly accessible repo, as I've been doing it all in a
>>>>> local branch from a pull from the main openhatch one. I probably should
>>>>> have
>>>>> just created a branch on gitorious and worked with it. I will next time.
>>>>>
>>>>> Here's a link to the plot progression (no sign in required):
>>>>> https://docs.google.com/document/d/16uZQWvvYWoWob2gjwCwqv24Wi9IRfllqCb5pw0oiu9c/edit?hl=en&authkey=CP2JvrIM
>>>>
>>>> Here is some early feedback. Some of it is "plot"-related feedback, which
>>>> can maybe get touchy -- if you had an artistic angle you were pushing
>>>> with
>>>> the choices you made, then totally explain that in a reply and we'll
>>>> figure
>>>> out how to make sure your artistic vision shines through.
>>>>
>>>> * On the first page, you wrote "the inded audience". Maybe "intended
>>>> audience"?
>>>>
>>>> * 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?
>>>>
>>>> * Dinner party:
>>>>
>>>> That would be awesome.
>>>>
>>>> --
>>>> -- Asheesh.
>>>>
>>>> http://asheesh.org/
>>>>
>>>> Q:      How many Martians does it take to screw in a light bulb?
>>>> A:      One and a half.
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel at lists.openhatch.org
>>>> http://lists.openhatch.org/mailman/listinfo/devel
>>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at lists.openhatch.org
>>> http://lists.openhatch.org/mailman/listinfo/devel
>>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQEcBAEBAgAGBQJNqjQXAAoJEI3j92WSe+b31R0H/A0LH43BgX3ZFqIVlL/WTLGy
>> +ATlsGyUZ5i/QF1zx3eqqXiMobPQHElJxujZEGCfJRvf/YoRKt3Bf6f4YHBBk+Ar
>> xBntlMoOX1mVRYEYDm7N6mnqmoUrUEcKv/OnbRsDtV8IUP7SQIh6tOEwk75OcPT+
>> +YQ3Qt/bV9hqR+gSP94lqKkxiGsni8PjIH+fITDrmSv6F+xk+IbAFKOH261tb0+a
>> XBhZkuxHsG6a/orKjMwBKwODThSPJ+jpAiIM3gbccZ6BOJIccdz9mDKAO+S3FuO+
>> 8xFLTePbTko0u0ayZptLrt4GP9skQ98mp2z87b4Z13fPcpZGy0XZVwWJ85B/06c=
>> =m93F
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.openhatch.org
>> http://lists.openhatch.org/mailman/listinfo/devel
>>
> _______________________________________________
> Devel mailing list
> Devel at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/devel
>