| «< Previous | Next »> |
A study of how Digital Humanists use GitHub, conducted by Lisa Spiro and Sean Morey Smith, found that a wide range of users, including professors, research staff, graduate students, IT staff, and librarians commonly used the site in their DH work. They used GitHub for a diverse range of activities, such as:
Participants in the study said they found GitHub useful in their Digital Humanities work for several reasons. In particular, it facilitated:
As you can see across these sessions, we use GitHub to host workshop curricula. Hosting 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. It also facilitates attribution and citation by clearly tracking which content was created by whom, when it was added, and which projects or materials are derived from others.
If you look just under the workshop title, dhsouthbend/git at the top of this page, you can see it is forked from DHRI-Curriculum/git. That line shows that this particular repository is building on (“forked from”) the curriculum for a session presented at the June 2018 Institute held at the CUNY Graduate Center. 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.
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 Track Changes functionality in Microsoft Word.
Patrick Sweeney wrote in 2018, “I personally have had Word crash and sections of an article lost, when I was 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 would always be 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 included in the discussion but was cut for space.”
Have you ever had a folder full of multiple and conflicting versions of documents that looked like this?
|
--Documents
|
--syllabus.doc
--syllabus2.doc
--syllabusnew.doc
--syllabusRevised.doc
--syllabusFINAL.doc
--syllabus?.doc
Many of us borrow and adapt from syllabi that colleagues have shared with us. This common and collegial practice has some challenges, however. When colleagues email around Word documents, it becomes difficult to identify who has created which assignments or language, and we may never see helpful innovative approaches that are developed later.
If colleagues instead forked syllabi from each other’s repositories on Github, individual work would be attributed, and further revisions and additions could be tracked. Versions from previous semesters could be called back and old assignments reincorporated.
Later in this workshop, you will create your own syllabus, track different versions of it, and replicate (“push”) your local version to GitHub. With luck, this will give you a sense of how some of the above workflows might work in practice.
| «< Previous | Next »> |