Code4Lib Norcal 2017

Revision as of 20:28, 21 June 2017 by ChristinaHarlow (Talk | contribs)

Revision as of 20:28, 21 June 2017 by ChristinaHarlow (Talk | contribs)

Code4Lib NorCal Summer 2017 Meeting

August 10th, 2017 || 9 AM to 5 PM || Lathrop Library on the Stanford University campus

Link to this page:

About

We're holding a free Code4Lib Northern California (NorCal) regional meeting & unconference on August 10, 2017. This meeting will be held at Lathrop Library, Stanford University. The day will be a mix of scheduled/planned and impromptu sessions, workshops, lightning talks, and break-outs.

Call for Sessions

Registration Link

Schedule

Information about getting to + around Stanford

Here is some information to get to Stanford:

Here is a map of the Stanford Campus for getting to Lathrop Library:

Note: the Marguerite buses are free to ride on the Stanford campus (include a link to the bus maps and schedules).

Expectation of Code4Lib NorCal Participants and Code4Lib NorCal Event Code of Conduct

NorCal Event & Planning Contacts

If you have any questions or concerns about this meeting, you can contact us: - on the #norcal channel on the Code4Lib Slack; - on the Code4Lib NorCal Google Group; - or email Chris Beer and Christina Harlow directly.

If you would like to help with planning, thank you! We are keeping all planning information, confirmed details, and participation steps is in this open Google document:

Planning Working Document in Google Drive

Feel free to add a comment or volunteer to take a task on. And thank you!

About Code4Lib NorCal

For more information on Code4Lib Northern California, review this collection of pages which also has details from past events, join the Code4Lib NorCal Google Group, and/or join the Code4Lib #norcal Slack Channel.

If you want to propose, collaborate on planning, or support Code4Lib Northern California event(s) in 2017 or in the future, use the Google Group and/or the Slack channel to alert your regional neighbors (who can help, give feedback, highlight possible schedule conflicts, etc.).