diff --git a/docs/source/code-of-conduct.rst b/docs/source/code-of-conduct.rst new file mode 100644 index 000000000..243ac8c6c --- /dev/null +++ b/docs/source/code-of-conduct.rst @@ -0,0 +1,126 @@ +Code of Conduct +=============== + +All participants in the fsspec community are expected to adhere to a Code of Conduct. + +As contributors and maintainers of this project, and in the interest of +fostering an open and welcoming community, we pledge to respect all people who +contribute through reporting issues, posting feature requests, updating +documentation, submitting pull requests or patches, and other activities. + +We are committed to making participation in this project a harassment-free +experience for everyone, treating everyone as unique humans deserving of +respect. + +Examples of unacceptable behaviour by participants include: + +- The use of sexualized language or imagery +- Personal attacks +- Trolling or insulting/derogatory comments +- Public or private harassment +- Publishing other's private information, such as physical or electronic + addresses, without explicit permission +- Other unethical or unprofessional conduct + +Project maintainers 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 behaviours that they deem inappropriate, +threatening, offensive, or harmful. + +By adopting this Code of Conduct, project maintainers commit themselves +to fairly and consistently applying these principles to every aspect of +managing this project. Project maintainers who do not follow or enforce +the Code of Conduct may be permanently removed from the project team. + +This code of conduct applies both within project spaces and in public +spaces when an individual is representing the project or its community. + +If you feel the code of conduct has been violated, please report the +incident to the fsspec core team. + +Reporting +--------- + +If you believe someone is violating theCode of Conduct we ask that you report it +to the Project by emailing community@anaconda.com. All reports will be kept +confidential. In some cases we may determine that a public statement will need +to be made. If that's the case, the identities of all victims and reporters +will remain confidential unless those individuals instruct us otherwise. +If you believe anyone is in physical danger, please notify appropriate law +enforcement first. + +In your report please include: + +- Your contact info +- 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 publicly available record + please include a link. +- Any extra context you believe existed for the incident. +- If you believe this incident is ongoing. +- If you believe any member of the core team has a conflict of interest + in adjudicating the incident. +- What, if any, corrective response you believe would be appropriate. +- Any other information you believe we should have. + +Core team members are obligated to maintain confidentiality with regard +to the reporter and details of an incident. + +What happens next? +~~~~~~~~~~~~~~~~~~ + +You will receive an email acknowledging receipt of your complaint. +The core team will immediately meet to review the incident and determine: + +- What happened. +- Whether this event constitutes a code of conduct violation. +- Who the bad actor was. +- Whether this is an ongoing situation, or if there is a threat to anyone's + physical safety. +- If this is determined to be an ongoing incident or a threat to physical safety, + the working groups' immediate priority will be to protect everyone involved. + +If a member of the core team is one of the named parties, they will not be +included in any discussions, and will not be provided with any confidential +details from the reporter. + +If anyone on the core team believes they have a conflict of interest in +adjudicating on a reported issue, they will inform the other core team +members, and exempt themselves from any discussion about the issue. +Following this declaration, they will not be provided with any confidential +details from the reporter. + +Once the working group has a complete account of the events they will make a +decision as to how to response. Responses may include: + +- Nothing (if we determine no violation occurred). +- A private reprimand from the working group to the individual(s) involved. +- A public reprimand. +- An imposed vacation +- A permanent or temporary ban from some or all spaces (GitHub repositories, etc.) +- A request for a public or private apology. + +We'll respond within one week to the person who filed the report with either a +resolution or an explanation of why the situation is not yet resolved. + +Once we've determined our final action, we'll contact the original reporter +to let them know what action (if any) we'll be taking. We'll take into account +feedback from the reporter on the appropriateness of our response, but we +don't guarantee we'll act on it. + +Acknowledgement +--------------- + +This CoC is modified from the one by `BeeWare`_, which in turn refers to +the `Contributor Covenant`_ and the `Django`_ project. + +.. _BeeWare: https://beeware.org/community/behavior/code-of-conduct/ +.. _Contributor Covenant: https://www.contributor-covenant.org/version/1/3/0/code-of-conduct/ +.. _Django: https://www.djangoproject.com/conduct/reporting/ + +.. raw:: html + + diff --git a/docs/source/index.rst b/docs/source/index.rst index b642ff833..40d6963e8 100644 --- a/docs/source/index.rst +++ b/docs/source/index.rst @@ -119,6 +119,7 @@ The current list of known implementations can be found as follows async.rst api.rst changelog.rst + code-of-conduct.rst These docs pages collect anonymous tracking data using goatcounter, and the