Code of Conduct

LDCX is an inclusive, friendly and  safe forum.  LDCX was conceived and executed as a collaborative, community-focused event. We are committed to facilitating helpful and respectful communication in a safe, diverse atmosphere. As an unconference, LDCX focuses on enabling the full and enthusiastic participation of all attendees.

LDCX organizers are dedicated to providing a harassment-free conference experience for everyone regardless of gender, gender identity, gender expression, sexual orientation, disability, physical appearance, body size, race, ethnicity or religion. We do not tolerate harassment of event participants in any form. 

Participants asked, by anyone, to stop any harassing behavior are expected to comply immediately. Event participants violating these rules may be sanctioned or expelled at the discretion of the organizers, and their details provided to partner institutions and events (see Sanctions).

If you are being harassed or have any other concerns, please contact a member of the event staff immediately (see Getting Help).

Getting Help

There are several ways to get in touch with conference duty officers.

  • In-person: Trained duty officers will be identifiable by distinctive name tags and lanyards with blue and white stripes.
  • Call or text +1 (650) 334-6927. The phone associated with this number will be in the posession of the primary duty officer on call during a given shift.
  • If you are unable to reach a duty officer during business hours, call Jib Supavadee Kiattinant at (650) 724-5455, our department's administrative assistant, who will contact individual duty officers directly to follow up.
  • Email ldcx-conduct@lists.stanford.edu. This email list is separate from the conference organizers’ administrative email group and will be monitored throughout the event by the duty officers listed below.
  • Direct message any of the individuals listed below on the code4lib Slack team.

Duty Officers

  • Erin Fahy (@efahy on Code4lib Slack)
  • Hannah Frost (@hannah on Code4lib Slack)
  • Christina Harlow (@cm_harlow on Code4lib Slack)
  • Jessie Keck (@jkeck on Code4lib Slack)
  • Mark A. Matienzo (@anarchivist on Code4lib Slack)
  • Jack Reed (@mejackreed on Code4lib Slack)
  • Sarav Shah (@saravshah on Code4lib Slack)
  • Camille Villa (@camillevilla on Code4lib Slack)

Duty Officer Shifts

Additional Resources and Contacts

Incident Protocol

Incident

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

LDCX 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 Escalation.

Escalation

If the offender insists that they did not offend, if the offender is actively harassing you, or if direct engagement is not a good option for you at this time, then you will have assistance of event organizers.

Find an event organizer in person, on Slack, or email (see details in Getting Help) They will assist you by providing accommodations and/or exercising Sanctions as necessary.

Resolution

If the incident results in corrective action, the community should support the decision made by organizers 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 organizers run into issues implementing the CoC, then the organizers will take these into context in the next event planning cycle, including possible revisions to the CoC as they see fit and possible outreach to external communities for insight or guidance on avoiding similar issues in the future.

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 here is have constructive discussions that lead to something tangible (affirmation of decision, change in CoC, modify decision, etc,).

Examples

  • Offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, age, race, or religion.
  • Unwelcome comments regarding a person's lifestyle choices and practices, including those related to food, health, parenting, drugs, and employment.
  • Deliberate misgendering, ignoring pronouns, use of 'dead' or rejected names.
  • Gratuitous or off-topic sexual images or behaviour in spaces where they're not appropriate.
  • Physical contact without consent or after a request to stop.
  • Stalking or following, deliberate intimidation, or threats of violence.
  • Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
  • Harassing photography or recording, including logging online activity for harassment purposes.
  • Sustained disruption of discussion.
  • Unwelcome sexual attention.
  • Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others.
  • Continued one-on-one communication after requests to cease.
  • Deliberate "outing" of any aspect of a person's identity without their consent, except as necessary to protect vulnerable people from intentional abuse.
  • Publication of non-harassing private communication.

Sanctions

Participants asked to stop any harassing behavior are expected to comply immediately. Failure to comply will result in sanctions, which 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 recording 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 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)
  • notifying appropriate individuals at the harasser’s home institution of the behavior
  • notifying organizers of other community events of the behavior 
  • publishing an account of the harassment

Social Rules

In order to create an inclusive, safe, and open work environment, LDCX participants are asked to follow a set of rules designed by the Recurse Center, previously the Hacker School. In their own words, 'the goal [of the Recurse Center Social Rules] isn't to burden everyone with a bunch of annoying rules, or to give us a stick to bludgeon people with for "being bad." Rather, these rules are designed to help all of us build a pleasant, productive, and fearless community.'

As such, these four rules are a lightweight set of explicit social norms to curtail specific kinds of behavior found to be destructive to a supportive, productive, and fun learning/working environment. The four rules are listed here; you can read more about them at http://recurse.com/manual#sub-sec-social-rules.

  • "No feigning surprise." You shouldn't act surprised when someone says they don't know something. There is no benefit to feigning surprise, and regardless of intent, it makes someone feel bad, or worse, about admitting that they don't know something.

  • "No well-actually's." This is when someone says something almost, but not entirely correct, and another person responds with "well, actually," and gives a correction that doesn't help move the conversation forward. That's not to say we don't care about truth or precision, but we want people to be aware of how and when they correct people, and whether or not it contributes to the goals of the conversation.

  • "No back-seat driving." If you overhear other people working through a problem, don't just intermittently toss advice in without engaging.

  • "No subtle -isms". This last rule bans racism, sexism, homophobia, transphobia, and other kinds of bias. Subtle -isms are small things that make others feel uncomfortable, and might be familiar as they're under the term "microagressions."

Tip of the hat here also to Mark Matienzo, who wrote the additional text explaining each of these rules in the context of a collaborative environment. We've paraphrased or, in places, extended Matienzo's work here.

Session Roles

As an unconference, LDCX focuses on enabling the full and enthusiastic participation of all attendees. In each session, we encourage assigning at least one participant to each of the following roles: Facilitator, Notekeeper, Timekeeper, and Gatekeeper (adapted from the Ada Initiative).

  • Facilitator

    • Your job is to present the topic and keep the session moving forward

    • Attempt to be neutral and fair as you guide the session

    • If you want to be a major participant in the discussion, hand off your facilitator duties to another person

    • If you have any time guidelines, give them to the timekeeper

    • Pay attention to people’s emotions and signals and respond to them

  • Notekeeper
    • Your job is to record important points, conclusions, resources, etc.

    • To share your notes with others at the conference, use the #ldcx channel on the code4lib Slack group

  • Timekeeper

    • Your job is to keep people aware of time and help them use it productively

    • Let people know at 15 minutes left and 5 minutes left

    • At the end of the session, interrupt and tell people the session is officially over

    • If people want to continue the discussion, ask them to move out of the room

  • Gatekeeper

    • Your job is to keep the discussion productive and respectful

    • Ask for clarification re: terminology, acronyms, avoid inside jokes

    • Periodically step into the discussion and see if people who haven’t said anything yet would like to

    • Politely interrupt people who have been talking too long

    • Redirect discussion back on-topic if it gets derailed

    • Reach out to an organizer, on behalf of the session’s audience, as needed to handle any Code of Conduct issues or violations within a session.

Resources

This Code of Conduct is adapted from the following organizations:

accessibilityaccessprivsarrow-circle-rightaskus-chataskus-librarianbarsblogsclosecoffeecomputercomputersulcontactsconversationcopierelectricaloutleteventsexternal-linkfacebook-circlegroupstudyhoursindividualinterlibrarynewsnextoffcampusopenlateoutdoorpeoplepolicypreviousprinterprojectsquietreservesscannersearchstudysupportingtabletourstwitter-circleworking