Everybody who participates in ecoCompute Science in one way or another is required to conform to this Code of Conduct (CoC). This includes authors, session participants, reviewers, shepherds, committee members and organisers.

The CoC applies before, during and after the event. It covers the discussion sessions, the review process and any related online space.

The organisers form the Code of Conduct team and are primarily responsible for handling any incidents. The team can be reached at science@eco-compute.io. The individual members and their direct contact details will be published on this page before the event.

We would like to thank the DjangoCon Europe 2019 CoC team for their Code of Conduct, which has been adapted here with minor modifications.

Why do we have a Code of Conduct?

Our goals with having this Code of Conduct are:

Helping everyone feel safe and included. Attendees may have had poor experiences in other events, or may be first-timers. We want to set the expectation that harassment and other unpleasant behaviour are not acceptable. This way, people who do have an unpleasant experience know that it is neither the norm nor acceptable to us as a community.

Helping to build trust that if an incident is reported, we will not respond with victim blaming, and that we will proceed with a thorough investigation. This will be true even if the incident involves someone in a position of power, for example.

Informing everyone of the expected behaviour. We are a diverse community, and having a Code of Conduct makes the expectations over everybody’s behaviour explicit and transparent.

The Code of Conduct is the basis for dealing with a report, assessing whether the CoC was violated, and what action should be taken.

Our Code of Conduct

We ask each attendant to keep the community in mind and do their best to foster a positive environment for everyone.

Behavior that contributes to a positive environment includes:

  • Being kind and considerate to others
  • Behaving professionally
  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Being supportive towards newcomers

We are dedicated to providing a harassment-free experience for everyone, regardless of race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.

We do not tolerate harassment of participants in any form. This includes offensive comments related to the categories above, deliberate intimidation, stalking, following, unwanted recording or screenshotting of sessions, sustained disruption of a session, violent threats or language, and unwelcome sexual attention. Advocating for, or encouraging, any of the above behaviour is also not acceptable.

Sexual language and imagery are not appropriate in any space to which the CoC applies.

Some people may not wish to be recorded or to appear on camera. Respect that. Sessions are not recorded by default, and nobody is required to switch on a camera.

Be careful in the words that you choose. Remember that sexist, racist, and other exclusionary jokes can be offensive and unwelcoming to those around you. Excessive swearing and offensive jokes are not appropriate at ecoCompute Science.

Condescending behavior towards people of different knowledge levels, and especially beginners, is unacceptable.

No one owes anyone any form of interaction or explanation for why they don’t want contact. If someone asks you to leave them alone, accept and respect it without any further discussion, even if you think it is unwarranted.

Where does the Code of Conduct apply?

This Code of Conduct applies to all ecoCompute Science spaces. That includes, but is not limited to:

  • The online platform the sessions run on
  • The review process, in both directions: how reviewers write about authors and how authors respond to reviewers
  • Correspondence with the committees and the organisers
  • Chat channels, posts carrying the event hashtag, and other online media
  • Informal gatherings that grow out of the event, whether or not they appear on the programme

What can happen if the CoC is violated?

In case of a Code of Conduct violation, some of the most common actions organisers may take are:

  • Demanding that a participant stops their behaviour.
  • Demanding that a participant prevents further contact with certain other participants.
  • Removing a participant from a session, or from the event, without refund.
  • Removing a reviewer from the review of a submission, or from the committee.
  • Withdrawing a submission from the programme.
  • Removing content from the published session notes.
  • The action taken is at the discretion of the Code of Conduct team. Participants are expected to comply immediately, and further action may be taken in case a participant does not comply. A record will be kept of all incidents.

Where to report incidents

If a Code of Conduct incident happens to you, or you witness it happening to someone else, please contact the CoC team immediately by sending an email to science@eco-compute.io. During a session you can also message any organiser directly.

Your report will be treated confidentially and will only be discussed within the CoC team.

The team members are named on this page and are present in the sessions. You can message any of them at any time to discuss an incident or concern.

Guidelines for reporting incidents

Please do not feel like you may be a burden to us by reporting incidents. Even if you happen to report multiple incidents during the event. We rather consider reports as an opportunity for us to act: by knowing about an incident, we can act on it, and often prevent it from going on or occuring again. But if we don’t know, we can’t take action.

If you’re not sure if an incident was already reported by someone else, even if many people saw it, please report it. It is frequent that several people witness an incident and no one reports it, because everyone thought other people would.

If you are not sure whether the situation was a Code of Conduct violation, or whether it applied to that particular space, we encourage you to still report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. And knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.

If you think you witness something, but you’re not sure what you saw, or you don’t have proof, it’s still very useful to us if you can report on that. You don’t have to build up a case before reporting, and it’s ok to report things even if you have doubts.

In your report please include, when possible:

  • Your contact info (so we can get in touch with you)
  • Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well.
  • When and where the incident occurred. Please be as specific as possible.
  • Your account of what occurred. If there is a written record (e.g. tweets or slack messages), please include screenshots and, if possible, a link.
  • Any extra context relevant for the incident.
  • If this incident is ongoing.
  • Any other information you would like to give us.

If you don’t have some of this information, or not at this time, please still make the report anyways. You can contact us at any time after your report if you want to add, edit or take back any information you shared.

If you feel unsafe reporting yourself, you may choose someone to represent you. In this case, we’d need their contact information, but we’d ask this person to make clear that they are not reporting in their own name.

When handling a report, we follow our response guidelines.

We value your participation, and look forward to seeing you at ecoCompute Science.