You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CODEOFCONDUCT.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,17 +35,22 @@ This Code of Conduct applies to all spaces managed by the Project whether they b
35
35
36
36
## Community Responsibilities
37
37
38
-
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.
38
+
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.
39
39
40
40
## Project Administrator Responsibilities
41
41
42
42
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.
43
43
44
44
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.
45
45
46
+
The list of project administrators, who are also Project Pythia's Principal Investigators (PIs), can be seen as follows:
Instances of unacceptable behavior can be brought to the attention of the project administrator(s), via the @ProjectPythia/core GitHub handle and/or projectpythia@ucar.edu, 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.
53
+
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 projectpythia@ucar.edu (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.
49
54
50
55
Instances of unacceptable behavior may also be reported:
51
56
- To [The Chief Human Resources Officer](chro@ucar.edu) 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
58
63
59
64
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).
60
65
66
+
## Confidentiality
67
+
**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.
68
+
69
+
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.
70
+
71
+
If a public statement is necessary, the identities of all individuals involved will remain confidential unless those individuals instruct us otherwise.
72
+
73
+
## Conflicts of Interest
74
+
75
+
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.
76
+
61
77
## Consequences
62
78
63
79
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.
0 commit comments