== Instructions ==Thank you for considering proposing a prePre-conference! Here conferences are a few details:NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions.
* We will be taking pre-conference proposals until '''November 7, 2014'''== Preconference Schedule ==* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]* If you are interested in ''attending'' a particular pre-conference, please append your name See below that proposal (indicating interest in more than one proposal is fine!)* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbiafurther information on each session.edu or collie@msu.edu* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions* Please use the template for proposals provided in the pre-formatted block below
{| class=== Proposal formatting guidelines"wikitable sortable"|-! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1: ===30 PM - 4:30 PM)|-| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Presentations workshop (1: Needs: projector/screen)|-| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector) |-| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || [[code4lib/Write The Docs barcamp]] (5)|-| '''Broadway I & II (70)''' || Linked Data Workshop (56: Bringing their own projector) || Intro to Git & possibly beyond (40: Needs: projector/screen)|-| '''Broadway III & IV (70)''' || Visualizing Library Data (60: Needs: projector) || Intro to Docker (52)|-| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (1: Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)|-| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating - must be in this room - limit 20 attendants)|-| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)|-| '''Studio (35)''' || (Empty) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)|-| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)|-| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || DPLA API Workshop (34: Bringing their own projector) |}
<pre>== Pre-conferences =====MORNING:======= Coding Custom Solutions for Every Department in the Library with File Analyzer ====* Terry Brady, Georgetown University Library, twb27@georgetown.edu
=== Preconference TitleThe Georgetown University Library has shared an application called the [http: ===//georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library. * Analyzing Marc Records for the Cataloging departmentOne of:* Transferring ILS invoices for the University Account System for the Acquisitions department '''"Full Day"''' * Delivering patron fines to the Bursar’s office for the Access Service department'''"Half Day [Morning]"''' * Summarizing student worker timesheet data for the Finance department'''"Half Day [Afternoon]"''' * Validating counter compliant reports for the Electronic Resources department* Preparing ingest packages for the Digital Services department* Validating checksums for the Preservation department
* Facilitator's name, affiliation, This hands on workshop will step through the components of the application framework and email address* Second facilitator's name, affiliation, email address, if second speakerthe process of customizing the application.
Abstract'''TRAINING OUTLINE'''* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015
====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====
* Karen A. Coombs, OCLC, coombsk@oclc.org
''Interested in Attending'' If Have you would be interested in attendingbuilt something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, please indicate by adding we will discuss a set of recommended best practices for how to share your name (but not email address, etccode.) here ###
</pre> == Pre-conference Proposals == Post We’ll start with coding standards and test writing so you can be confident of the quality of your ideas here! === Delivering code. Next we'll discuss inline documentation as a tool for developers and Preserving GIS Data === '''Half Day [Morning]'how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.
==== Delivering and Preserving GIS Data ====
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu
* Eliot Jordan, Princeton University
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.
''Interested in Attending'[https://stanford.box.com/geohydra-code4lib2015 Slides]''' [http://slides.com/eliotjordan/practical-experience-with-geoserver/ Slides (GeoServer)]
If you would be interested in attending====Linked Data Workshop====* Karen Estlund, please indicate by adding your name (but not email addressUniversity of Oregon, etckestlund@uoregon.) hereedu* Tom Johnson, DPLA, tom@dp.la
# [[UserDeveloper and metadata experts-focused linked data workshop. Topics covered will include:Ssimpkin|Sarah Simpkin]]# Vicky Steeves#linked open data principles, converting existing data, and modeling linked data in DAMS.
=== A hand's on introduction to GeoBlacklight ===[http://goo.gl/QrUIYE LD Workshop Materials]
'''Half Day [Afternoon]''' * Darren Hardy, Stanford University, drh@stanford.edu* Jack Reed, Stanford University, pjreed@stanford.edu GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data". ''Interested in Attending'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # [[User:Ssimpkin|Sarah Simpkin]]# Vicky Steeves# ====RailsBridge: Intro to programming in Ruby on Rails==='''"Half-Day" [morning]'''=
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome
''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''
To help the class run smoothly please complete the install fest before attending the class. If you have problems contact us!
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].
''Interested in Attending'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Maura Carbone#Vicky Steeves# ==== Replace yourself with a painfully complex bash script...or try Ansible ==='''Half Day [Morning]'''=
* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org
Abstract:
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.
''Interested in Attending''====Visualizing Library Data====* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs
If you would be interested in attending, please indicate by adding Visualizing your name (but not email addressinstitution’s data can give new insight about your holding’s strengths, etcweaknesses and outliers.) here### === Intro They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to Docker ==='''Half Day [Whenever]'''start producing visualization with their own data.
* John Fink, McMaster University, john dot fink at gmail dot com* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com Abstract: [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end. ''Interested in Attending'' 1. Jim Hahn === Code Retreat FULL DAY:==='''Full Day'''
====Code Retreat====
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.
Abstract:
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]
''Interested in Attending''====Code4Arc ====* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com
=== Presentations workshop === '''"Half Day [Afternoon]"''' (but could be expanded based on interest)What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?
* Chris BeerCode4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, Stanford University, cabeer@stanfordand the particular challenges of developing archival systems.edu* Additional facilitators welcome Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking The schedule may include the following:* Panel type conversations about offering lightning talksthe State of Art in Archives * Case Studies - discussion of workflows at specific institutions, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity including gaps in tools and how those are being addressed or could be addressed * Tool Demos - access to rehearse your presentationdemos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, get feedback from peersArchivematica, get familiar with the presentation technologyBitCurator, etc. ''Interested in Attending''AtoM)
If you would be interested in attendingArtefactual will provide demos running Archivematica and AtoM, please indicate by adding your name (but not email addressLyrasis will do so for ArchivesSpace, etcBitCurator will for BitCurator.) We encourage others to chime in hereto expand the list of tools available to touch and play with.
#Vicky Steeves## === Dive into Hydra === One of:'''"Half Day [Afternoon]"''' * Justin CoyneWhen signing up, Data Curation Experts, justin@curationexperts.com* Bess Sadler, Stanford University, bess@stanford.edu Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building openplease indicate if you are an end-source software. Dive into Hydra is user or a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshopdeveloper.
''Interested in Attending''
# Laney McGlohon - developer
# Shaun Ellis
# Ryan Rotter - sysadmin/developer
# Matt LaChance
# Maureen Callahan - archivist, often-times product owner
# Liza Harrell-Edge - end-user
# Jessica Venlet - end-user/archivist (can be there in the afternoon)
# Andrew Berger - "digital" archivist
# Bill Kelm - sysadmin
# Jeremy Floyd - end-user (archivist turned metadata librarian)
# Sara Amato (morning only) - end-user
# Julie Hardesty (afternoon only) - end-user (metadata librarian)
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Maura Carbone## === =[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp ]==== One of:'''"Full Day"''', with options for jumping in for half a day
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA
Abstract'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''
''Placeholder Documentation. We all know that we need it for now - more information will be available before the proposal deadlinethings we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what'. More information about s stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs at http://docsconference, and is home for many folks who live and breathe documentation.writethedocsThis barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.org/
There will be Remember, like metadata, documentation is a nominal fee (t/b/d) for non-Code4LibCon attendees (subject love note to organizer approval)the future.
''Interested in Attending''More information about Write the Docs at http://conf.writethedocs.org/ There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).
If you would be interested in attending===AFTERNOON:======= A hands-on introduction to GeoBlacklight ====* Darren Hardy, please indicate by adding your name (but not email addressStanford University, etcdrh@stanford.) hereedu* Jack Reed, Stanford University, pjreed@stanford.edu
'''Full day'''###GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".
'''Morning'''==== CollectionSpace: Getting it up and running at your museum ====#* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org##* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org
'''Afternoon'''###This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections.
=== Linked Data Workshop ===If possible, please bring a laptop capable of running the latest version of VirtualBox (www.virtualbox.org). I've prepared a VirtualBox machine for the workshop that I will share with you at the beginning of the session.
One of:==== Dive into Hydra ===='''"Full Day"''' * Justin Coyne, Data Curation Experts, justin@curationexperts.com*
* Karen Estlund, University Hydra is a collaboration of Oregon, kestlund@uoregonover 30 educational institutions who work together to solve their repository needs by building open-source software.edu* Tom Johnson Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, DPLA, tom@dpenabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.la
Abstract==== DPLA API Workshop:====* Audrey Altman, DPLA* Mark Breedlove, DPLA* Mark Matienzo, DPLA* Tom Johnson, DPLA
Developer-focused linked data The Digital Public Library of America API workshopguides attendees through the process of creating an app based on DPLA's free, public API. More info The API provides access to comeover 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.
If you would be interested in attending, please indicate by adding your name (but not email address, etc'''[http://bit.) herely/c4l15-dpla-api Slides and resources]'''
# Logan Cox==== Fail4Lib 2015 ====#* Andreas Orphanides, akorphan (at) ncsu.edu#* Jason Casden, jmcasden (at) ncsu.edu
'''[https://docs.google.com/presentation/d/1pdatzBjVIs1YDQL3CUhWjvSj_u5Y-9pOLZvb-PAdUaU/edit?usp=== Archivematica for users and developers ===sharing SLIDES]'''
One Failure. Failure never changes. Since failure is an inescapable part of:our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let'"Full Day"''s train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we' ll do so with grace and without fear.
* Sarah Romkey, Artefactual Systems, sromkey@artefactualThis year's preconference will include new case studies and an improved discussion format.com* Justin Simpson, Artefactual SystemsRepeat customers are welcome! (Fail early, jsimpson@artefactualfail often.com)
AbstractThe schedule may include the following:* Case studies. Avoid our own mistakes by bearing witness to the failures of others.* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.
This is a workshop intended for both end-users of Archivematica (librarians, archivists, systems administrators) as well as developers who are interested in Archivematica feature development, or use of Archivematica back-end features for integration into other projects.''Readings''
In the morning, the end-users will meet with Sarah for a hands-on Archivematica training session. We will discuss processing configurations, use cases, and installation/hosting options for Archivematica. We will also demonstrate DIP upload to Archivematica's access system, AtoM. During this time, developers will meet with Justin and other Artefactual developers for a hackaton style session focusing on Archivematica development and integration''Case Study 1: The Healthcare.gov rollout'''
For the afternoon, we plan to bring the two groups together to discuss, share use cases* [http://www.theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how-government-can-do-tech-better Adrianne Jeffries (The Verge): Thanks a lot, and have breakout sessions focused on specific topics that arose from the morning and afternoon sessionshealthcare. gov]
When signing up, please indicate if you are an end* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-user or a developermanagement/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]
If you would be interested in attending* Optional, please indicate by adding your name nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (but not email addressnpEngage): Lessons learned from the healthcare.gov rollout]* Optional, etcvery enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech) here: The hyperscale lessons of healthcare.gov]
###'''Case Study 2: The Challenger disaster'''
* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]
** This is designed as an instructor's guide, but the summary material beginning on page 3 stands on its own as a case study report. The instructor's materials on the first couple pages are also worth reading.
=== Fail4Lib 2015 ==='''Half Day * [TBD, probably afternoonhttp://www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]'''
Contacts: * Andreas OrphanidesOptional, akorphan (at) ncsugood technical detail: [http://en.eduwikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]* Jason Casden, jmcasden Optional: [http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt Richard Feynman: Appendix F: Personal observations on the reliability of the Shuttle (atRogers Commission excerpt) ncsu.edu]
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important ==== Intro to be familiar with itDocker ====* John Fink, to acknowledge itMcMaster University, and to grow from it -- andjohn dot fink at gmail dot com* Francis Kayiwa, in contravention to longstanding tradition, to accept it as a fact University of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This wayMaryland Libraries , when we do what we do -- and fail fkayiwa at what we do -- we'll do so with grace and without fear.umd dot edu
This [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year's preconference . This workshop will include new case studies take you through the basic features of Docker, including setup, importing of containers, development workflows and an improved discussion formatdeploying. Repeat customers are welcome! (Fail earlyKnowing when Docker is useful and when it isn't will also be covered. Ideally, fail oftenevery attendee will have ample experience creating and running their own Docker instances by the end.)
The schedule may include the following:==== Intro to Git & possibly beyond ====* Erin Fahy, Stanford University, efahy@stanford.edu* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu
* Case studies. Avoid our own mistakes by bearing witness to We can start with the failures basics of othersGit and discuss ways in which it can help you version control just about any file, not just code.Points we can go over:* Confessionals, for those willing to share. LetWhat is a Distributed Version Control System?* What's learn from our own (the difference between Git and each others') failuresGithub.com?* Group therapy. Vent about your own experiences in How to initialize new Git projects locally and on a judgment-free setting. Explore how we can make our organizations less risk-averse remote server/Github* Cloning/Forking existing projects and more failure-tolerant.keeping up to date* The wonderful world of Git branches* Interactive rebasing* Contributing code to existing projects & what pull requests are* How to handle merge conflicts* Overview of workflows and branch best practices* (time allowing) Advanced git: pre/post hooks, submodules, anything else?
''Interested in attending''==== Presentations workshop ====* Chris Beer, Stanford University, cabeer@stanford.edu* Additional facilitators welcome.
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you would be interested in attending're preparing a talk for this year's Code4Lib, please indicate by adding this workshop is an opportunity to rehearse your name (but not email addresspresentation, get feedback from peers, get familiar with the presentation technology, etc.) here ###
[[Category:Code4Lib2015]]
