View source for Reporting Guide

= Code of Conduct Reporting Guide =
As a member of this community, you may remind other members when their behavior is not in line with the Code of Conduct. Please be sure that you are also following the spirit of the Code of Conduct when reminding others of it.

For those who do not want to directly reach out in this situation, we encourage you to email conduct@open-zfs.org -- even in situations that are not explicitly stated in the Code of Conduct. 

'''All reports will be kept confidential.''' In some cases we may determine that a public statement will need to be made in order to inform the broader community. If this need arises, the identities of all parties involved will remain confidential to the extent possible unless those individuals instruct us otherwise.

'''If you believe anyone is in physical danger, please notify appropriate law enforcement first.''' If you are unsure what law enforcement agency is appropriate, please include this in your report and we will attempt to notify them.

We encourage you to report incidents, even if you are unsure whether the incident is a violation, or whether the space where it happened is covered by this Code of Conduct. We would much rather have a few extra reports where we decide to take no action, than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. Knowing about incidents that are not violations, or happen outside our spaces, can help us to improve the [[Code of Conduct]] and the processes surrounding it.

== Information to include in your report ==
The more information you provide to the Working Group, the better equipped they will be in their investigation. All reported incidents will be investigated, regardless of whether all of this information is provided. 			
* Contact information for the reporter including name, email, and phone number. 
* You may report incidents anonymously if you are uncomfortable providing your contact information. However, this may hamper the investigation.
* The names of all people directly involved in the incident, including relevant nicknames or pseudonyms.
* Include witness names if possible
* Time and forum/location where the incident occurred. Be specific.
* Details about what happened. Note any supporting materials, such as message screencaps, IRC logs, or emails.
* Additional context for the situation, if appropriate.
* Whether or not the incident is ongoing.
* Any additional information that is relevant to investigating and resolving the incident

==What happens after you file a report?==
You will receive an email from the OpenZFS Code of Conduct Working Group acknowledging receipt immediately. The current Working Group members are:
* Matt Ahrens, matt@mahrens.org
* Joshua Clulow, josh@sysmgr.org
* Karyn Ritter, karyn.ritter@gmail.com

The Working Group will immediately meet to review the incident and determine:
* What happened based on the perspective of all involved.
* 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.

We promise to acknowledge receipt within 48 hours (and will aim for a faster response). 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. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe.

Once the Working Group has a complete account of the events, they will make a decision as to how to respond. Responses may include:
* Private actions
** Nothing (if we determine no violation occurred).
** A private gentle reminder of the Code of Conduct.
** A private reprimand from the Working Group to the individual(s) involved.
* Public actions
** A public gentle reminder to the community about behavior out of step withof the Code of Conduct. For example, unacceptable behavior that occurs in a public forum.
** An imposed vacation (i.e. asking someone to "take a week off" from a mailing list, Slack, or IRC).
** A temporary (for a specified time) or indefinite ban from some or all OpenZFS spaces (mailing lists, Slack, IRC, events, etc.)

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.

== What if your report concerns a possible violation by a Working Group member? ==
The entire Code of Conduct Working Group will see all incident reports sent to conduct@open-zfs.org. Anyone directly involved in the incident will be immediately recused and will not participate in any discussions of the incident or its resolution.
* If you are uncomfortable submitting a report that will be seen by a person involved in the incident, you can instead send the report directly to the other members of the Working Group for resolution. See email addresses for current Working Group members above.

== Additional Information about the Code of Conduct ==
* [[Code of Conduct Summary]]
* [[Code of Conduct]]
* [[Working Group and Code of Conduct Mechanics]]

== Attribution ==
Borrowed heavily from the great work done by [https://www.djangoproject.com/conduct/ | Django], [https://www.contributor-covenant.org/version/1/4/code-of-conduct | Contributor Covenant], [https://golang.org/conduct | Go], [https://stackoverflow.com/conduct | Stack Overflow], and the [http://web.archive.org/web/20141109123859/http://speakup.io/coc.html | Speak Up! project]. Text all covered by CC-BY-SA