Update CODEOFCONDUCT.md (ProjectPythia#553)

* Update CODEOFCONDUCT.md

* Update CODEOFCONDUCT.md

* Update CODEOFCONDUCT.md

Add GitHub profile links for each profile picture

* Update CODEOFCONDUCT.md

remove leftover MyST card directive

* Update myst.yml to add CoC to navbar

* Brian's fix

Co-authored-by: Brian Rose <[email protected]>

---------

Co-authored-by: Brian Rose <[email protected]>

Author: erogluorhan

CODEOFCONDUCT.md

@@ -35,17 +35,22 @@ This Code of Conduct applies to all spaces managed by the Project whether they b
 
 ## Community Responsibilities
 
-Everyone in the community is empowered to respond to people who are showing unacceptable behavior. They can talk to them privately or publicly. Anyone requested to stop unacceptable behavior is expected to comply immediately. If the behavior continues concerns may be brought to the project administrators or to any other party listed in the Reporting section below.
+Everyone in the community is empowered to respond to people who are showing unacceptable behavior. They can talk to them privately or publicly. Anyone requested to stop unacceptable behavior is expected to comply immediately. If the behavior continues, concerns may be brought to the project administrators (Read the next section to see who they are) or to any other party listed in the Reporting section below.
 
 ## Project Administrator Responsibilities
 
 Project administrators are responsible for clarifying the standards of acceptable behavior and are encouraged to model appropriate behavior and provide support when people in the community point out inappropriate behavior. Project administrator(s) are normally the ones that would be tasked to carry out the actions in the Consequences section below.
 
 Project administrators are also expected to keep this Code of Conduct updated with the main one housed at UCAR, as listed below in the Attribution section.
 
+The list of project administrators, who are also Project Pythia's Principal Investigators (PIs), can be seen as follows:
+
+|[![Brian Rose](https://github.com/brian-rose.png)](https://github.com/brian-rose)<br>Brian Rose|[![John Clyne](https://github.com/clyne.png)](https://github.com/clyne)<br>John Clyne|[![Orhan Eroglu](https://github.com/erogluorhan.png)](https://github.com/erogluorhan)<br>Orhan Eroglu|[![Ryan May](https://github.com/dopplershift.png)](https://github.com/dopplershift)<br>Ryan May|[![James Munroe](https://github.com/jmunroe.png)](https://github.com/jmunroe)<br>James Munroe|
+|:-:|:-:|:-:|:-:|:-:|
+
 ## Reporting
 
-Instances of unacceptable behavior can be brought to the attention of the project administrator(s), via the @ProjectPythia/core GitHub handle and/or [email protected], who may take any reasonable and necessary action to address and stop the behavior. However, making a report to a project administrator is not considered an ‘official report’ to UCAR.
+Instances of unacceptable behavior can be brought to the attention of the project administrator(s), either by directly reaaching out to one of them (see the previous section for their individual GitHub profiles) or via the [`@ProjectPythia/core`](https://github.com/orgs/ProjectPythia/teams/core) GitHub handle and/or [email protected] (the latter two may include more people than the project administrators though), who may take any reasonable and necessary action to address and stop the behavior. However, making a report to a project administrator is not considered an ‘official report’ to UCAR.
 
 Instances of unacceptable behavior may also be reported:
 - To [The Chief Human Resources Officer]([email protected]) who serves as UCAR’s Section 504, Title VI, VII and IX Coordinator;
@@ -58,6 +63,17 @@ If you require a reasonable accommodation due to a disability or for assistance
 
 Any Contributor can use these reporting methods even if they are not directly affiliated with UCAR. The Frequently Asked Questions (FAQ) page for reporting is [here](https://www.ucar.edu/who-we-are/ethics).
 
+## Confidentiality
+**All reports will be kept confidential**. When we discuss incidents with people who are reported, we will anonymize details as much as we can to protect reporter privacy.
+
+However, some incidents happen in one-on-one interactions, and even if the details are anonymized, the reported person may be able to guess who made the report. If you have concerns about retaliation or your safety, please note those in your report. We still encourage you to report so that we can support you while keeping our community members safe. In some cases, we can compile several anonymized reports into a pattern of behavior and take action on that pattern.
+
+If a public statement is necessary, the identities of all individuals involved will remain confidential unless those individuals instruct us otherwise.
+
+## Conflicts of Interest
+
+If a member of the project administrators has a conflict of interest regarding a report, they will recuse themselves from discussing and handling the incident. They will not have access to the incident documentation, and they will excuse themselves from any conversations involving handling the incident.
+
 ## Consequences
 
 Upon receipt of a complaint, the project administrator(s) may take any action deemed necessary and appropriate under the circumstances. Such action can include things such as: removing, editing, or rejecting comments, commits, code, wiki edits, email, issues, and other contributions that are not aligned to this Code of Conduct, or banning temporarily or permanently any contributor for other behaviors that are deemed inappropriate, threatening, offensive, or harmful. Project administrators also have the right to report violations to UCAR HR as well as to a contributor’s home institution and/or law enforcement. In the event an incident is reported to UCAR, UCAR will follow its Complaint and Investigations Procedure.

portal/myst.yml

@@ -33,6 +33,7 @@ project:
     - file: cookbook-guide.md
     - file: quick-cookbook-guide.md
     - file: metrics.md
+    - file: ../CODEOFCONDUCT.md
 
 site:
   domains: []