2018 Code4Lib Midwest Meeting
- 1 Location
- 2 Call for proposals
- 3 Registration
- 4 Logistics
- 5 Schedule
- 6 Programming Sign-up
- 7 Code of Conduct
Miami University of Ohio
Call for proposals
To help us make sure we have a room for you to present in, we encourage you to submit a proposal by the end of March, 2018. Unless we get a tremendous amount of proposals we do not anticipate rejecting submissions.
Link to submit your presentation
Registration for this conference is free and does not require joining a national organization. Due to space limits, registration will be limited to 50 participants. Similar to the national Code4lib, we have a meal sign-up page for lunch on January 7th, which allows us to keep registration costs low for you.
Link to conference registration
There are airport shuttles to Oxford from either Dayton or Cincinnati airports.
More information on travel to campus
Hampton Inn Oxford, OH This is a newly constructed hotel near near campus, and within walking distance. We do not have a room block.
Miami University is a member of Eduroam, and public wireless is available on campus.
Coffee, tea, and pastries will be sponsored by Miami University Libraries on June 7th. For all other meals check our list of local dining options on and around campus.
You are highly encouraged to take public transportation if possible; but getting to Miami may be easiest by car. Parking and transit information
Eat, Drink, Do Fun Things
Working on a Google Map with a few dining suggestions near campus
Contact Craig Boman at email@example.com
June 7, 9a-5p
June 8, 9a-12p
Outline of June 7
8:30-9:00: Check-in and breakfast
9:00-9:15: Welcome and introductory remarks
9:15-10:15: Introductions and potential keynote speaker
10:00-11:30 Lightning Talks/presentations
11:30-1:00 Lunch (Sign up)
1:00-2:30 Presentations/ Breakouts (4) (post-breakout lightning talks to report back)
Time TBD (~5PM-~8PM): Meetup at [http:// TBD] This bar is an easy bus ride from campus, and near many great dining options.
Outline of June 8
9:00-10:30 Presentations and/or lightning talks
11:00-12:00 Wrap-up |
Code4Lib Midwest programming depends on the folks attending the conference. Please consider giving a presentation or lightning talk, or submitting your ideas for a hackfest/breakout session.
Share what you are working on! Add your name and a description below. Please also let us know how long you'll need (10 or 20 minutes), and whether you prefer Wednesday or Thursday (or if it doesn't matter). Contact Ryan Wick (firstname.lastname@example.org) with your preferred username to set up a Code4Lib wiki account. If you don't have a wiki account and don't want to sign up for one, please email email@example.com.
Title - Presenter, Affiliation
Have something cool to share but you don't want to be in front of the room for more than 5 minutes? Lightning talks are for you. 5 minute max. Sign up now or at the conference:
- Title - Presenter
Actual breakout sessions presented and locations will be determined on June 7. Please propose an idea here if you are willing to facilitate a discussion on a topic.
Code of Conduct
Code4Lib seeks to provide a welcoming, fun, and safe community and conference experience and ongoing community for everyone. We do not tolerate harassment in any form. Discriminatory language and imagery (including sexual) is not appropriate for any event venue, including talks, or any community channel such as the chatroom or mailing list. Harassment is understood as any behavior that threatens another person or group, or produces an unsafe environment. It includes offensive verbal comments or non-verbal expressions related to gender, gender identity, gender expression, sexual orientation, disability, physical appearance, body size, race, age, religious beliefs, sexual or discriminatory images in public spaces (including online), deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
Read and contribute to our full Code of Conduct document on GitHub