Interactive Visualization with Git

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
(Directions:)
(Suggestions to Open Source Mentors)
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
{| border="1"
 
|-
 
|'''Title''' ||  Git: Interactive Visualization
 
|-   
 
|'''Overview''' ||  Students learn from an interactive visual git simulator / game. This activity focuses on LOCAL Git functionality (such as that on your laptop, NOT remote internet-based code repositories).
 
  
See [[Git_Activity_4]] for the next in the series.
+
{{Learning Activity Overview
|-
+
|title=
|'''Prerequisite Knowledge''' || [[Git_Activity]] and [[Git_Activity_2]] or an introductory understanding of what SCM is about, and basic git commands.
+
Git: Interactive Visualization
|-
+
|overview=
|'''Learning Objectives''' ||Students will be able to ...
+
Students learn from an interactive visual git simulator / game. This activity cover both local (on your laptop) and remote (internet-based code repository) Git functionality.
 
+
|prerequisites=
* Create a branch.
+
[[Intro to GitHub (Activity)]] and [[Work Locally with Git from the Command Line (Activity)]] or an introductory understanding of what SCM is about, and basic git commands.
* Checkout a branch.
+
|objectives=
* Create a tag.
+
* Create and checkout a branch.
* Checkout a tag.
+
* Create and checkout a tag.
 
* Merge a branch into another.
 
* Merge a branch into another.
 
* Rebase a branch onto another.
 
* Rebase a branch onto another.
Line 33: Line 28:
 
* Delete a remote branch.
 
* Delete a remote branch.
 
* Push changes into a remote repository after remote history has diverged.
 
* Push changes into a remote repository after remote history has diverged.
 +
|process skills=
 +
}}
  
|}
+
=== Background ===
  
=== Background: ===
+
''Is there background reading material?''
Is there background reading material?
+
 
* All material is provided in this assignment, though references below may be useful:
 
* All material is provided in this assignment, though references below may be useful:
 
** http://git-scm.com/doc
 
** http://git-scm.com/doc
** [[Git_Activity]]
+
** [[Intro to GitHub (Activity)]]
** [[Git_Activity_2]]
+
** [[Work Locally with Git from the Command Line (Activity)]]
  
What is the rational for this activity?
+
''What is the rational for this activity?''
 
* Getting familiar with git from the command line is not easy. This activity makes it a game!
 
* Getting familiar with git from the command line is not easy. This activity makes it a game!
  
 +
=== Directions ===
  
=== Directions: ===
 
 
* Go to tutorial at: http://pcottle.github.io/learnGitBranching/
 
* Go to tutorial at: http://pcottle.github.io/learnGitBranching/
* Complete all activities under the <u>'''Main'''</u> and <u> '''Remote''' </u> tabs
+
* Complete all activities under the <u>'''Main'''</u> and <u>'''Remote'''</u> tabs
  
 
[[File:LocalGit.png|600px]]
 
[[File:LocalGit.png|600px]]
  
* Take screenshots of your solutions, AS YOU GO through each section
+
{{Learning Activity Info
** 15 sections in all, so 15 screenshots
+
|acm unit=
* Init, commit, and then create a remote repo (on github or elsewhere online) of your screenshots
+
SE - Software Engineering / SE Tools and Environments
** REMINDER: reuse of open source code is encouraged; submission of someone else's answers is academic plagiarism and will be enforced
+
|acm topic=
 
+
Software configuration management and version control
=== Deliverables: ===
+
|difficulty=
* Send URL / link of remote internet-accessible repository to instructor.
+
Medium, as the advanced commands become more difficult to follow.
* 15 Screenshots of the solutions of each section, with commits
+
|time=
 
+
2-4 hrs
 
+
|environment=
=== Assessment: ===
+
{| border="1" class="wikitable"
+
! Criteria
+
! Partial Credit
+
! Complete Credit
+
 
+
|-
+
| '''Screenshots'''
+
| Bad file naming, difficult directory structure, or less than 15 screenshot files
+
| Easy to view files, no weird naming, all 15 screenshots
+
 
+
|-
+
| '''Solutions'''
+
| Not all solutions given, or some solutions are not optimal (hard to tell from screenshot though)
+
| All solutions given and most are optimal (sometimes optimality is not necessary for completion)
+
 
+
|}
+
 
+
 
+
=== Comments: ===
+
What are some likely difficulties that an instructor may encounter using this activity?
+
* Students might easily plagiarize or copy each others screenshots to the solutions.
+
* To fight this, a REMINDER has been added in the directions.
+
* Teachers might also mentioned it in-class and spot-check for it in grading.
+
 
+
 
+
=== Additional Information: ===
+
{| border="1"
+
|-
+
|'''Knowledge Area/Knowledge Unit''' || SE - Software Engineering / SE Tools and Environments from [[ACM_Body_of_Knowledge]]
+
|-
+
|'''Topic''' ||  Software configuration management and version control
+
|-
+
|'''Level of Difficulty''' || Medium, as the advanced commands become more difficult to follow
+
|-
+
|'''Estimated Time to Completion''' || 2-4 hrs
+
|-
+
|'''Materials/Environment''' ||
+
 
* Access to Internet/Web and web browser
 
* Access to Internet/Web and web browser
 
* Github account (or any online Git hosting)
 
* Github account (or any online Git hosting)
|-
+
|author=
|'''Author''' ||  Stoney Jackson, Nick Yeates
+
Stoney Jackson, Nick Yeates
|-
+
|source=
|'''Source''' || http://pcottle.github.io/learnGitBranching/
+
http://pcottle.github.io/learnGitBranching/
|-
+
|license=
|'''License''' ||
+
 
The MIT License (MIT)
 
The MIT License (MIT)
 
Copyright (c) 2012 Peter Cottle
 
Copyright (c) 2012 Peter Cottle
|}
+
}}
  
 +
=== Suggestions to Open Source Mentors ===
  
=== Suggestions to Open Source Mentors: ===
 
 
Suggestions for an open source community member who is working in conjunction with the instructor.
 
Suggestions for an open source community member who is working in conjunction with the instructor.
 
* Mentors might show what websites and resources (Stackoverflow, IRC, etc) they often utilize when they are stuck or something unexpected happens upon committing or branching.
 
* Mentors might show what websites and resources (Stackoverflow, IRC, etc) they often utilize when they are stuck or something unexpected happens upon committing or branching.
Line 121: Line 78:
  
  
--------------------
+
[[Category:Learning_Activity]]
 
+
[[Category: Learning_Activity]]
+
 
[[Category:Communication_and_Tools]]
 
[[Category:Communication_and_Tools]]
 +
[[Category:Git]]
 +
[[Category:CS2]]
 +
[[Category:Good Draft]]

Latest revision as of 17:21, 8 March 2017


Title

Git: Interactive Visualization

Overview

Students learn from an interactive visual git simulator / game. This activity cover both local (on your laptop) and remote (internet-based code repository) Git functionality.

Prerequisites

Intro to GitHub (Activity) and Work Locally with Git from the Command Line (Activity) or an introductory understanding of what SCM is about, and basic git commands.

Learning
Objectives
After successfully completing this activity, the learner should be able to:
  • Create and checkout a branch.
  • Create and checkout a tag.
  • Merge a branch into another.
  • Rebase a branch onto another.
  • Cherry-pick commits.
  • Use relative commit references to refer to commits.
  • Move branches to a different commit.
  • Detach and move around HEAD.
  • Explain the difference between a branch, a tag, and HEAD.
  • Clone a remote repository.
  • Fetch changes from a remote repository.
  • Merge changes from a remote repository.
  • Rebase changes from a remote repository.
  • Describe the difference between _rebase_ and _merge_.
  • Push changes into a remote repository.
  • Describe the relationship between `git fetch`, `git merge`, and `git pull`
  • Describe the relationship between `git fetch` and `git push`.
  • Delete a remote branch.
  • Push changes into a remote repository after remote history has diverged.
Process Skills
Practiced


Background

Is there background reading material?

What is the rational for this activity?

  • Getting familiar with git from the command line is not easy. This activity makes it a game!

Directions

LocalGit.png

ACM BoK
Area & Unit(s)

SE - Software Engineering / SE Tools and Environments

ACM BoK
Topic(s)

Software configuration management and version control

Difficulty

Medium, as the advanced commands become more difficult to follow.

Estimated Time
to Complete

2-4 hrs

Environment /
Materials
  • Access to Internet/Web and web browser
  • Github account (or any online Git hosting)
Author(s)

Stoney Jackson, Nick Yeates

Source

http://pcottle.github.io/learnGitBranching/

License

The MIT License (MIT) Copyright (c) 2012 Peter Cottle


Suggestions to Open Source Mentors

Suggestions for an open source community member who is working in conjunction with the instructor.

  • Mentors might show what websites and resources (Stackoverflow, IRC, etc) they often utilize when they are stuck or something unexpected happens upon committing or branching.
    • What troubleshooting steps do they use in their head?
    • Do they chat or talk to fellow project-members or work colleagues?
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox