Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • fmortreu-master-patch-11d2
  • origin_hicstuff
  • dev
  • modified_containers
  • hicstuff
  • nico
  • TEMPLATE
  • nf-core-template-merge-2.7.2
  • nf-core-template-merge-2.7.1
  • nf-core-template-merge-2.6
  • nf-core-template-merge-2.5.1
  • nf-core-template-merge-2.5
  • nf-core-template-merge-2.4
  • nf-core-template-merge-2.3.2
  • nf-core-template-merge-2.3.1
  • nf-core-template-merge-2.3
  • nf-core-template-merge-2.2
  • nf-core-template-merge-2.1
  • nf-core-template-merge-2.0.1
  • 1.3.0
  • 1.2.2
  • 1.2.1
  • 1.2.0
  • 1.1.0
  • 1.0.0
26 results
Blame Permalink
CODE_OF_CONDUCT.md 8.87 KiB

Code of Conduct at nf-core (v1.0)

Our Pledge

In the interest of fostering an open, collaborative, and welcoming environment, we as contributors and maintainers of nf-core, pledge to making participation in our projects and community a harassment-free experience for everyone, regardless of:

  • Age
  • Body size
  • Familial status
  • Gender identity and expression
  • Geographical location
  • Level of experience
  • Nationality and national origins
  • Native language
  • Physical and neurological ability
  • Race or ethnicity
  • Religion
  • Sexual identity and orientation
  • Socioeconomic status

Please note that the list above is alphabetised and is therefore not ranked in any order of preference or importance.

Preamble

Note: This Code of Conduct (CoC) has been drafted by the nf-core Safety Officer and been edited after input from members of the nf-core team and others. "We", in this document, refers to the Safety Officer and members of the nf-core core team, both of whom are deemed to be members of the nf-core community and are therefore required to abide by this Code of Conduct. This document will amended periodically to keep it up-to-date, and in case of any dispute, the most current version will apply.

An up-to-date list of members of the nf-core core team can be found here. Our current safety officer is Renuka Kudva.

nf-core is a young and growing community that welcomes contributions from anyone with a shared vision for Open Science Policies. Open science policies encompass inclusive behaviours and we strive to build and maintain a safe and inclusive environment for all individuals.

We have therefore adopted this code of conduct (CoC), which we require all members of our community and attendees in nf-core events to adhere to in all our workspaces at all times. Workspaces include but are not limited to Slack, meetings on Zoom, Jitsi, YouTube live etc.

Our CoC will be strictly enforced and the nf-core team reserve the right to exclude participants who do not comply with our guidelines from our workspaces and future nf-core activities.

We ask all members of our community to help maintain a supportive and productive workspace and to avoid behaviours that can make individuals feel unsafe or unwelcome. Please help us maintain and uphold this CoC.

Questions, concerns or ideas on what we can include? Contact safety [at] nf-co [dot] re

Our Responsibilities

The safety officer is responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behaviour.

The safety officer in consultation with the nf-core core team have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Members of the core team or the safety officer who violate the CoC will be required to recuse themselves pending investigation. They will not have access to any reports of the violations and be subject to the same actions as others in violation of the CoC.

When are where does this Code of Conduct apply?

Participation in the nf-core community is contingent on following these guidelines in all our workspaces and events. This includes but is not limited to the following listed alphabetically and therefore in no order of preference:

  • Communicating with an official project email address.
  • Communicating with community members within the nf-core Slack channel.
  • Participating in hackathons organised by nf-core (both online and in-person events).
  • Participating in collaborative work on GitHub, Google Suite, community calls, mentorship meetings, email correspondence.
  • Participating in workshops, training, and seminar series organised by nf-core (both online and in-person events). This applies to events hosted on web-based platforms such as Zoom, Jitsi, YouTube live etc.
  • Representing nf-core on social media. This includes both official and personal accounts.