SpECTRE Documentation Coverage Report
Current view: top level - __w/spectre/spectre/docs/Contributing - ReportingGuide.md Hit Total Coverage
Commit: 2ae2b99409ac582030d56a4560a92a3e066a7e54 Lines: 0 1 0.0 %
Date: 2022-01-15 08:40:38
Legend: Lines: hit not hit

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

Generated by: LCOV version 1.14