Skip to content

Commit

Permalink
more content added
Browse files Browse the repository at this point in the history
  • Loading branch information
pswee001 committed May 15, 2018
1 parent 393a5da commit e8178ef
Showing 1 changed file with 14 additions and 3 deletions.
17 changes: 14 additions & 3 deletions sections/examples.md
Expand Up @@ -23,14 +23,25 @@ Participants in the study said they found GitHub useful in their Digital Humanit
## How We Use GitHub:

### Sharing and Attribution
As you can see across the workshops this week, here at GCDI we use GitHub to host workshop curricula. Hosting the sessions on GitHub allows you (and anyone else interested in these topics!) to follow our repositories, and create your own version of the workshop based on our materials. This fosters open scholarship and knowledge sharing, as well as facilitating attribution and citation by clearly tracking which content was created by whom, and when it was added. If you look just under the workshop title at the top of this page, you can see it is "forked from pswee001/Git_DRI_Jan_2018." That shows that this particular repository is building on ("forked from") the curriculum for a session I presented at our January 2018 Institute. If you then look at that repository, you will see that it is in turn forked from previous sessions that were developed by other GC Digital Fellows for workshops in past years.
As you can see across the workshops this week, at GCDI we use GitHub to host workshop curricula. Hosting the sessions on GitHub allows you (and anyone else interested in these topics!) to follow our repositories, and create your own version of the workshop based on our materials. This fosters open scholarship and knowledge sharing, as well as facilitating attribution and citation by clearly tracking which content was created by whom, and when it was added.
#### Case 1: This Workshop!
If you look just under the workshop title at the top of this page, you can see it is "forked from pswee001/Git_DRI_Jan_2018." That shows that this particular repository is building on ("forked from") the curriculum for a session I presented at our January 2018 Institute. If you then look at that repository, you will see that it is in turn forked from previous sessions that were developed by other GC Digital Fellows for workshops in past years.

### Collaborative Writing
Some of us use Git to track changes (*version control* in Git parlance) in writing projects, and find it to be a cleaner, more elegant solution than the tracked changes fucntion in a Microsoft Word document. I personally have had Word crash, and sections of an article lost, when collaborating on a large writing project with co-authors who were using different versions of Word! If we had tracked our revisions using Git, the previous versions of the paper are always saved and changes documented in case we wanted to return to an idea from an earlier draft, or a section that reviewer 3 *really* wants to see in included in the discussion but was originally cut for space.
Some of us use Git to track changes (*version control* in Git parlance) in writing projects, and find it to be a cleaner, more elegant solution than the tracked changes function in a Microsoft Word document.
##### Case 2: Co-authored Publications
I personally have had Word crash, and sections of an article lost, when collaborating on a large writing project with co-authors who were using different versions of Word! If we had tracked our revisions using Git, the previous versions of the paper are always saved and changes documented in case we wanted to return to an idea from an earlier draft, or a section that reviewer 3 *really* wants to see in included in the discussion but was originally cut for space.

## How You Could Use GitHub: Syllabi
### How You Could Use GitHub

Have you ever had a folder full of multiple and conflictiong versions of documents that looked like this?
syllabus.doc syllabus2.doc syllabusnew.doc syllabusRevised.doc syllabusFINAL.doc syllabus?.doc

Many of us, especially if it's a new prep, borrow and adapt from syllabi that colleagues have shared with us. For example, when I first taught, I was offered syllabi by colleagues who had taught the course before. I utilized some of their work as a base to build my particular course, and after developing my own syllabi I happily emailed them to other graduate students teaching for the first time. This common and collegial practice has some challenges, however. As my colleagues and I emailed around Word documents, it became difficult to identify who had created which assignments or language, and we rarely got to see how others developed innovative approaches that would be useful in our own classes.

#### Case 3: Syllabi
If my colleagues and I had instead forked our syllabi from eachother's repositories on GitHub, our individual work would be attributed, and we could follow eachother's revisions and additions to better revise our own. I could also easily go back to syllabi from previous semesters and dig up that classic or obscure reading that I wanted to reincorporate into the course.

Later in this workshop, you will fork an example syllabus I created, modify it to match your interests, and then push it back to GitHub. This exercise will show illustrate basic functions of Git and GitHub as well as demonstrating how collaboration and version control can be useful in scholarly applications such as course syllabi.

[<<< Previous](concept.md) | [Next >>>](commandline.md)

0 comments on commit e8178ef

Please sign in to comment.