Code of Conduct

Code of Conduct

The Research Data Access and Preservation (RDAP) Summit organizers are committed to providing an environment where all attendees can participate fully in the program and activities without fear of harassment or discriminatory behavior of any kind.

Harassment is understood as any behavior that threatens or demeans 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 or political 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.

This Code of Conduct applies to all spaces managed by the RDAP Summit organizers, including but not limited to the Summit, workshops, and community forums such as the email list. Participation in the Summit indicates an acceptance of this Code of Conduct and the procedures by which the Summit organizers resolve any Code of Conduct incidents.

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 they have affected you negatively. It is possible that the offending behavior is unintentional and the accidental offender and offended will resolve the incident by having that initial discussion.

The RDAP organizers recognize that there are many reasons why speaking directly to the offender may not be workable for you. 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 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 need a third party to step in.

If you are at the Summit or another RDAP event, find the Code of Conduct helper. They should be listed on the Summit website and designated by a nametag. If you can’t find the CoC helper, there will be other organizers available to help if the situation calls for immediate action.

We encourage you to talk to the CoC helper or another organizer directly so we can help immediately. However, if that is not possible, you can report the incident through the Incident Report Form or an email to the CoC helper (RDAPCOC@gmail.com).

For incidents on the listserv, the messages are not moderated but the list is maintained by the RDAP Board.

3. Wider community response to the 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 helper 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 helper in Step 2 runs into issues implementing the CoC, then the helper should come to the community with these issues and the community should revise the CoC as they see fit.

People will have opinions about how the CoC is enforced. Some 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.).

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 RDAP Summit or event, or banning the offender from the 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 responsibilities and privileges the harasser holds and requiring that the harasser not volunteer for future RDAP 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

RDAP Summit 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.

The organizers should have readily available the following information:

  • Conference organizer: [ORGANIZER NAME], [PHONE NUMBER]
  • [CONFERENCE HOTEL NAME]: [PHONE NUMBER]
  • [MUNICIPALITY] Police Department: [PHONE NUMBER]
  • [LOCAL SEXUAL ASSAULT/CRISIS LINE]: [PHONE NUMBER]
  • [TAXI COMPANY NAME]: [PHONE NUMBER]

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

We value everyone’s participation in the RDAP community, and will all work to keep the RDAP Summit a safe and friendly space for all participants!

Based on the Code4Lib Code of Conduct and the Carpentries Code of Conduct, which were both adapted from the example policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers.