Git and Github talk | osdpa | amia14 |
•Download as PPTX, PDF•
3 likes•1,026 views
Git and GitHub are version control tools that archivists and cultural heritage workers can use to collaborate on digital projects. The document introduces Git and GitHub, demonstrates how they work, and provides examples of how cultural institutions like the Library of Congress, BAVC, and WGBH use GitHub for archiving and digital preservation projects. Tutorials and links are included to help new users learn about Git and GitHub.
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Git and Github talk | osdpa | amia14 |
- 1. Introduction to Git and Github Lauren Sorensen Association of Moving Image Archivists Savannah, 2014
- 2. Git and Github What is Git? What is Github? How are these different? What is version control?
- 3. Git and Github demo
- 4. how do archivists and cultural heritage workers use git and github?
- 5. tutorials: https://help.github.com/ http://harishankarayandev.wordpress.com/2014/07/0 2/an-intro-to-git-and-github-for-newbies/ & many youtube videos, other intros. cultural heritage on Github: https://github.com/LibraryOfCongress .../BAVC .../umd-mith .../dericed .../AVPreserve .../WGBH .../amiaopensource
Editor's Notes
- At it’s most basic, Github.com is a collaborative, social media tool, that works with a version control system called Git. According to a recent article, has 6.8 million users and 15.2 million code repositories, more than double the respective numbers recorded two years ago. It’s mostly used by coders, but there are several cases where github has been used in alternate ways, like as a travel log (basically crowdsourcing through pushing and pulling from others places to go and be while traveling): https://github.com/dylanegan/travel and another, https://github.com/CMAA/nova-organi-harmonia
- Git is: version control system developed in 2005 as a part of the Linux system (original creator, with others’ contributions: Linus Torvalds) What is Git? Git is unique in version control systems for software in that it it works best for distributed or open source models, where community and non-linear, decentralized contributions are welcome. There are multiple checks, called “pushing” and “pulling” that those who are “committers” to a particular repo or application can gather from others in the community that wish to contribute. Github is: a social way to share versions of things (things being: historically mostly code and associated documentation), so making that community contribution easier. We’re going to run through a quick demo of how to use Git and Github.
- Sign up for an account here: https://github.com/ - and create a repo! Don’t create a readme.md. What follows are some simple instructions. There are also many tutorials out there, I’ll link to in a later slide. Commands in command line are labelled in bold: You can initialize a local repository by typing git init -The way git works is that it uses the filesystem to create a top level directory, that you control locally -So in typing git init having cd’ed into a a directory (using mkdir) called amia14 and there’s a nested folder beneath it called .git Triggered by actions you take to make versions that are captured in this local directory (still local right now - Github is just the networked part). By signing up for Github, we haven’t done any copying of code or capturing of code. git config --global user.name "laurensorensen" <- username from Github sign-up git config --global user.email "laurens@nyu.edu" <- email used with Github Files that are hidden in a Mac are labeled with a period in front: Show .git by using application called “tree” to see files used to help versioning. tree .git - it’s hidden, used as a way to store versions. info-objects-ref are where these versions are stored. So we’re going to make a .txt file in the directory we just created, amia14 (not .git, that is in that same folder to track whatever else is in it). We open a text editor (any), make the file video.txt. Now at this point, it is untracked but in the same folder as the .git hidden folder. In order to track it as a part of our git repo, we have to take some deliberate actions. First, we can check the status of the tracking of this doc by typing “git status” git status examines the working directory to look for files that are modified or are new git add video.txt adds the file to version control - to that local hidden .git version tracking. That doesn’t mean that it’s a permanent record of that file yet (kind of like a suggestion - adding it to the record and saving w/ more ease of working and futzing around without impacting other parts of the application or whatever else is in the repo that might function alongside this .txt file) git status to check - now we’re at the point where there are changes we want to add to the rest of the application, feel good about its affect and intention enough in the code to do that. git commit -m “my first commit” <- anything within the quotes is a desription of what happened to that document, in case you want to roll back changes and to describe what happened to others who might look at your public repo. means that the .txt is now merged into the branch, (in this case the master branch, that lives now on your local machine). Right now, this repository locally has no knowledge of the remote repo we first created on github.com - we’re going to change that now by going to your GitHub repository, in the right sidebar, copy the remote repository URL: https://github.com/laurensorensen/amia.git git remote add origin https://github.com/laurensorensen/amia.git git status git remote -v this verifies the new remote URL git push origin master this pushes the changes in your local repository up to the remote repository you specified as the origin terms not going over today: Forking: allows you as a Github user to begin helping an existing open source project (you can even fork those that say they have read-only access and ask for permission later to contribute, by submitting a “pull request”). Forking allows you to copy a repository and sends it to your own namespace (in other words, creates a complete copy of that repository in your own Github account) So now that it’s forked you can make changes and offer those changes back to the repository you forked from with a pull request back to original repo, basically asking their OK and enabling testing of your code by those who are allowed to commit to that original repository. Depending on the license (and perhaps some polite asking), you could even go branch off from the original and create your own application from that forked starting point, creating your own, new master.
- different uses for building software / finding software useful for cultural heritage orgs: Premisers (BAVC) - make premis records, recording actions in digital repository systems QCTools (BAVC) MOMA DRMC AMS (American Archive: blog post by Josh explains use case well) some of these are not out of the box (e.g. AMS), require some training and developer support but nonetheless, useful tools for our community. different use cases for different institutions: For distribution: example: LOC, uses for only this purpose, project management and development behind the scenes. For project management: PBCore - tracking requested changes in schema in Github. For collaborating on coding projects, OSS as described in last slide: forking, pushing and pulling - non-linearity Can search for simple scripts, keyword searching based on a need. “checksum” Where to get practical hands-on experience: Coding schools like even Lynda.com, many youtube tutorials, others. Flatiron (s/o Ashley Blewer), Hackbright, General Assembly, many others online.
- Existing projects: like most things in our field (steenbecks, film rewinds, professional analog video decks), digital pres and access is often a hybrid of production process use cases and making that work for archives - so tools that might pertain to working with digital files, analyzing them etc can work with archive purposes in mind, if not always the same use cases. Can be an entry point to working with IT, many scripts are best used run at intervals by a server Search the web, Stack Overflow for errors, take a break: Systems can be complex or daunting at first, next day or a few weeks from now they won’t seem simple, utilitarian.