Code4Lib 2016

The Code4Lib 2016 Philadelphia Committee is pleased to announce that we have finalized the dates and location of the 2016 conference.

The 2016 conference will be held from March 7 through March 10 in the Old City District of Philadelphia. This location puts conference attendees within easy walking distance of many of Philadelphia’s historical treasures, including Independence Hall, the Liberty Bell, the Constitution Center, and the house where Thomas Jefferson drafted the Declaration of Independence. Attendees will also be a very short distance from the Delaware River waterfront and will be a short walk from numerous excellent restaurants.

As we’ll be reserving almost all of the space within the hotel for our conference (both rooms and conference spaces), Code4Lib 2016 will have the tight-knit community feel we know is important.

More details to come soon; in the meantime, the Keynote Committee is gearing up to open submissions for the conference keynote speaker, so be sure to contact them at pacella@gmail.com for more information, or you can nominate a keynote speaker at http://wiki.code4lib.org/2016_Invited_Speakers_Nominations.

Also, our Sponsorship Committee is actively looking for sponsors for 2016, so please contact the committee via Shaun Ellis to learn about all the ways your organization can help sponsor our 2016 conference.

It’s shaping up to be a great conference this year, and there will be lots more opportunities to volunteer. Our team is looking forward to seeing you on March 7!

The Code4Lib 2016 Philadelphia Committee

Code4Lib Northern California: Stanford, CA

Stanford University Libraries will host a Code4Lib Northern California regional meeting on Tuesday, August 4, 2015 in the Lathrop Library on Stanford's campus. We'll have a morning session with lightning talks about various topics and an afternoon of smaller breakout and working sessions.

You can get more details about the event and register on the Code4Lib NorCal wiki page.

Code4Lib Journal #29

Code4Lib Journal #28: Special Issue on Diversity in Library Technology

Issue 28 of the Code4Lib Journal, Special Issue on Diversity in Library Technology, organized by eight special guest editors and two regular editors, is now available.

Topic: 

Code4Lib 2016 will be in Philadelphia

Code4Lib 2016 will be in Philadelphia, PA. The conference hosting proposal gives an idea of what it will be like. All necessary information will be available here as planning develops, and in the Code4Lib2016 category on the wiki.

Topic: 

Code4Lib 2016 Conference Proposals

Accumulated Proposals by closing date of 2015-02-20

Los Angeles Proposal - Los Angeles, CA

Philadelphia Proposal - Philadelphia, PA

Code4Lib Wiki 2016 Proposals Page - http://wiki.code4lib.org/2016_Hosting_Proposals

Host Voting is NOW OPEN 2015-02-23 00:00:00 UTC 2015-03-07 08:00:00 UTC. You can also watch the results.

Topic: 

Code4Lib North 2015: St. Catharines, ON

The sixth Code4Lib North meeting will be on June 4--5, 2015 at the St. Catharines Public Library, 54 Church St., St. Catharines, Ontario. St. Catharines is on the Niagara Peninsula on the south side of Lake Ontario, close to the American cities of Buffalo and Rochester in New York. See the wiki page for details and to sign up for a talk.

Topic: 

Code4Lib 2015 videos

All of Code4Lib 2015 was recorded and the videos are available on the YouTube Code4Lib channel.

2015 Code of Conduct

Code4Lib seeks to provide a welcoming, fun, and safe community and
conference experience as well as an 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.

Conflict Resolution

  1. Initial Incident

    If you are being harassed, notice that someone else is being harassed,
    or have any other concerns, and you feel comfortable speaking with
    the offender
    , please inform the offender that he/she/ze has affected you
    negatively. Oftentimes, the offending behavior is unintentional, and the
    accidental offender and offended will resolve the incident by having
    that initial discussion.

    Code4Lib recognizes that there are many reasons speaking directly to
    the offender may not be workable for you (including but not limited to
    unfamiliarity with the conference or its participants, lack of spoons,
    and concerns for personal safety). If you don't feel comfortable
    speaking directly with the offender for any reason, skip straight to
    step 2.

  2. Escalation

    If the offender insists that he/she/ze did not offend, if offender is
    actively harassing you, or if direct engagement is not a good option
    for you at this time, then you will need a third party to step in.

    If you are at a conference or other event, find an event organizer or
    staff person, who should be listed on the wiki.
    If you can't find an event organizer, there will be other staff
    available to help if the situation calls for immediate action.

    If you are in the #code4lib IRC, the zoia command to list people
    designated as channel helpers is @helpers. At most times, there is at least one helper in the channel.

    For the listserv, you have a free-for-all for public messages; however,
    the listserv does have a maintainer, Eric Lease Morgan.

  3. Wider community response to Incident:

    If the incident doesn't pass the first step (discussion reveals offense
    was unintentional, apologies said, public note or community is informed
    of resolution), then there's not much the community can do at this point
    since the incident was resolved without outside intervention.

    If incident results in corrective action, the community should support
    the decision made by the Help in Step 2 if they choose corrective action,
    like ending a talk early or banning from the listserv, as well as
    support those harmed by the incident, either publicly or privately
    (whatever individuals are comfortable with).

    If the Help in Step 2 run into issues implementing the CoC, then the
    Help should come to the community with these issues and the community
    should revise the CoC as they see fit.

    In Real Life people will have opinions about how the CoC is enforced.
    People will argue that a particular decision was unfair, and others will
    say that it didn't go far enough. We can't stop people having
    opinions, but what we could do is have constructive discussions
    that lead to something tangible (affirmation of decision, change in CoC,
    modify decision, etc,).

Sanctions

Participants asked to stop any harassing behavior are expected to comply
immediately. If a participant engages in harassing behavior, organizers may
take any action they deem appropriate, including warning the offender,
expulsion from the Code4Lib event, or banning the offender from a chatroom
or mailing list.

Specific sanctions may include but are not limited to:

  • warning the harasser to cease their behavior and that any further reports
    will result in other sanctions
  • requiring that the harasser avoid any interaction with, and physical
    proximity to, their victim for the remainder of the event
  • early termination of a talk that violates the policy
  • not publishing the video or slides of a talk that violated the policy
  • not allowing a speaker who violated the policy to give (further) talks at
    the event
  • immediately ending any event volunteer responsibilities and privileges the
    harasser holds requiring that the harasser not volunteer for future Code4lib
    events (either indefinitely or for a certain time period)
  • requiring that the harasser immediately leave the event and not return
  • banning the harasser from future events (either indefinitely or for a
    certain time period)
  • publishing an account of the harassment

Code4Lib event organizers can be identified by their name badges, and will
help participants contact hotel/venue security or local law enforcement,
provide escorts, or otherwise assist those experiencing harassment to feel
safe for the duration of the event. Code4Lib IRC volunteers can be identified
by issuing the @helpers command to the #code4lib bot named "zoia".

If an incident occurs, please use the following contact information:

  • Conference organizers: Tom Johnson, 360-961-7721 or Evviva Weinraub, 617-909-2913
  • Hilton Portland & Executive Tower: 503-226-1611
  • Portland Police Department: 503-823-0000
  • Portland Women's Crisis Line (24/7): 503-235-5333 (or toll-free: 888-235-5333) 24/7
  • Radio Cab: 503-227-1212
  • IRC channel administrators: anarchivist, mistym, mjgiarlo, ruebot; or enter @helpers in the IRC channel

We expect participants to follow these rules at all conference venues,
conference-related social events, community gatherings, and online communication channels.

We value your participation in the Code4Lib community, and your efforts to
keep Code4Lib a safe and friendly space for all participants!

Licensed under CC0

Based on the example policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers.

Code4Lib 2015 Diversity Scholarships

The Code4Lib Scholarship Committee will award 5 diversity scholarships based on merit and need. Each scholarship will provide up to $1,000 to cover travel costs and conference fees for a qualified attendee to attend the 2015 Code4Lib Conference, which will be held in Portland, Oregon, from February 9 - 12, 2015.

Applications are due by December 31, 2014 at 5 PM EST (see below for more details).

DIVERSITY SCHOLARSHIP ELIGIBILITY, CRITERIA, AND REQUIREMENTS

To qualify for a scholarship, an applicant must be interested in actively contributing to the mission and goals of the Code4Lib Conference.

  • Two scholarships will be awarded to any woman or transgender person.
  • Two scholarships will be awarded to any person of Hispanic or Latino, Black or African-American, Asian, Native Hawaiian or Pacific Islander, or American Indian or Alaskan Native descent.
  • One scholarship will be awarded to the best remaining candidate who
    meets any of the previously mentioned eligibility requirements.

Eligible applicants may apply based on multiple criteria, but no applicant will receive more than one scholarship. Past winners of any Code4Lib scholarship are not eligible for a scholarship.

The scholarship recipients will be selected based upon their merit and financial needs.

Registration spots are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference at this point. Scholarship recipients will receive a special link for free registration, or will be reimbursed if they have already registered.

Scholarship recipients are required to write and submit a brief trip report to the Code4Lib 2015 Scholarships Committee by April 1, 2015 to be posted to the Code4Lib wiki. The report should address: (a) what kind of experience they had at the conference, (b) what they have learned, (c) what suggestions they have for future attendees and conference organizers.

All reimbursement forms and receipts must be received by May 26, 2015.

HOW TO APPLY

To apply, please send an email to Francis Kayiwa (francis.kayiwa_at_gmail.com) with the subject heading Code4Lib 2015 Diversity Scholarship Application containing the following (combined into a single attached PDF, if possible):

  1. A brief letter of interest, which:
    • Identifies your eligibility for a diversity scholarship
    • Describes your interest in the conference and how you intend to
      participate
    • Discusses your merit and needs for the scholarship
  2. A resume or CV
  3. Contact information for two professional or academic references

The application deadline is Dec. 31, 2014, 5pm EST. The scholarship committee will notify successful candidates the week of Jan. 9, 2015.

SPONSORS

We would like to thank our sponsors for supporting the Code4Lib 2015 Diversity Scholarships. All sponsors have left it up to the discretion of the Code4Lib 2015 Scholarship Committee for how to award these diversity scholarships.

CONFERENCE INFORMATION

For more information on the Code4Lib Conference, please see the
conference website at http://code4lib.org/conference/2015. You can see write-ups of previous Code4Lib Conferences:

Pages

Subscribe to code4lib RSS