Open Source Comes to Campus/Curriculum/Saturday: Difference between revisions

From OpenHatch wiki
Content added Content deleted
imported>Paulproteus
imported>Paulproteus
No edit summary
Line 5: Line 5:
'''Pre-requisites''': Have some Linuxy distro and a terminal open, or Terminal on a Mac, or GitBash on Windows.
'''Pre-requisites''': Have some Linuxy distro and a terminal open, or Terminal on a Mac, or GitBash on Windows.


'''Learning objectives''': Have a general understanding of what paths mean (/usr /usr/bin /home etc.). Understand the purpose and basic use of package management tools. Understand how to "cd" and "ls" around in a terminal. Have familiarity with passing arguments to CLI programs (e.g., tar). Preferably, understand that a text terminal can display "graphical" (e.g. via ncurses) programs.
'''Learning objectives''': Have a general understanding of what paths mean (/usr /usr/bin /home etc.). Understand the purpose and basic use of package management tools. Understand how to "cd" and "ls" around in a terminal. Have familiarity with passing arguments to CLI programs (e.g., tar). Preferably, understand that a text terminal can display "graphical" (e.g. via ncurses) programs. Understand enough history of the command line to know it came "first." Have enough understanding of the command line to succeed at the rest of the day's activities.


'''Activity''':
'''Activity''':

Revision as of 21:42, 2 December 2011

Note well: This is just a draft; work in progress.

Linux and the command line

Pre-requisites: Have some Linuxy distro and a terminal open, or Terminal on a Mac, or GitBash on Windows.

Learning objectives: Have a general understanding of what paths mean (/usr /usr/bin /home etc.). Understand the purpose and basic use of package management tools. Understand how to "cd" and "ls" around in a terminal. Have familiarity with passing arguments to CLI programs (e.g., tar). Preferably, understand that a text terminal can display "graphical" (e.g. via ncurses) programs. Understand enough history of the command line to know it came "first." Have enough understanding of the command line to succeed at the rest of the day's activities.

Activity:

Assessment:

Ethics and history of open source; and economics and licensing that support it

Communication tools (IRC, mailing lists)

Getting, modifying, and verifying open source software (getting code; local patching)

Project organization (bug trackers; git format-patch; github; people's roles in a project)