Line data    Source code

       1           0 : \cond NEVER
       2             : Distributed under the MIT License.
       3             : See LICENSE.txt for details.
       4             : \endcond
       5             : # SpECTRE Code of Conduct - Reporting Guide {#reporting_guide}
       6             : 
       7             : \tableofcontents
       8             : 
       9             : If you believe someone is violating the code of conduct, you can
      10             : always file a report by emailing conduct@spectre-code.org, or discuss
      11             : it informally and confidentially with one of the project leaders.
      12             : **All reports will be kept confidential.**
      13             : 
      14             : If you believe anyone is in physical danger, please notify appropriate
      15             : law enforcement first. If you are unsure what law enforcement agency
      16             : is appropriate, please include this in your report and we will attempt
      17             : to notify them.
      18             : 
      19             : Reports of violations of the code of conduct can be as formal or
      20             : informal as needed for the situation at hand. If possible, please
      21             : include as much information as you can. If you feel comfortable,
      22             : please consider including:
      23             : - Your contact info (so we can get in touch with you if we need to
      24             :   follow up).
      25             : - Names (real, nicknames, or pseudonyms) of any individuals
      26             : involved. If there were other witnesses besides you, please try to
      27             : include them as well.
      28             : - When and where the incident occurred. Please be as specific as
      29             :   possible.
      30             : - Your account of what occurred. If there is a publicly available
      31             : record (e.g. a mailing list archive or Slack logs) please include a
      32             : link.
      33             : - Any extra context you believe existed for the incident.
      34             : - If you believe this incident is ongoing.
      35             : - Any other information you believe we should have.
      36             : 
      37             : ### What happens after you file a report?
      38             : 
      39             : You will receive an email from the Code of Conduct Committee or
      40             : project leader(s) you contacted, acknowledging receipt within 24 hours
      41             : (and we will aim to respond much quicker than that). We will review
      42             : the incident and try to determine:
      43             : - What happened and who was involved.
      44             : - Whether this event constitutes a code of conduct violation.
      45             : - Whether this is an ongoing situation, or if there is a threat to
      46             :   anyone’s physical safety.
      47             : 
      48             : Once the Code of Conduct Committee or contacted project leader(s) have
      49             : a complete account of the events we will make a decision on how to
      50             : respond, possibly in consultation with the full Executive Committee
      51             : (excluding anyone involved in the incident). Responses may include:
      52             : - Nothing, if we determine no violation occurred or it has already
      53             :   been appropriately resolved.
      54             : - Providing either moderation or mediation to ongoing interactions
      55             :   (where appropriate, safe, and desired by both parties).
      56             : - A private reprimand from the working group to the individuals
      57             :   involved.
      58             : - An imposed vacation (i.e. asking someone to “take a week off” from a
      59             :   mailing list or Slack).
      60             : - Escalation to the appropriate institutions.
      61             : - Involvement of relevant law enforcement if appropriate.
      62             : 
      63             : If the situation is not resolved within one week, we’ll respond within
      64             : one week to the original reporter with an update and explanation.
      65             : Once we’ve determined our response, we will separately contact the
      66             : original reporter and other individuals to let them know what actions
      67             : (if any) we’ll be taking. We will take into account feedback from the
      68             : individuals involved on the appropriateness of our response, but we
      69             : don’t guarantee we’ll act on it.
      70             : 
      71             : ### Code of Conduct Committee
      72             : 
      73             : The current members of the Code of Conduct Committee (and the only
      74             : people that see emails sent to conduct@spectre-code.org) are:
      75             : - Saul Teukolsky
      76             : - Harald Pfeiffer
      77             : 
      78             : SpECTRE is being developed in support of our collaborative Simulating
      79             : eXtreme Spacetimes (SXS) research program into the multi-messenger
      80             : astrophysics of neutron star mergers, core-collapse supernovae, and
      81             : gamma-ray bursts.  As such, it falls under the managerial oversight of
      82             : the SXS Executive Committee whose current members are:
      83             : - Matthew Duez
      84             : - Francois Foucart
      85             : - Lawrence Kidder
      86             : - Geoffrey Lovelace
      87             : - Harald Pfeiffer
      88             : - Mark Scheel
      89             : - Leo Stein
      90             : - Saul Teukolsky
      91             : - Aaron Zimmerman
      92             :