Skip to content

Commit 92855af

Browse files
authored
Update CODE_OF_CONDUCT.md
1 parent 6c44794 commit 92855af

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

CODE_OF_CONDUCT.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Examples of behaviors that contribute to a positive environment include:
2020
Examples of unacceptable behavior include, but are not limited to:
2121

2222
- Harassment, intimidation, or discrimination in any form
23-
- Physical, verbal, or written abuse by anyone to anyone, including repeated use of pronouns other than those requested
23+
- Physical, verbal, or written abuse by anyone to anyone
2424
- Unwelcome sexual attention or advances
2525
- Personal attacks directed at other guests, members, participants, etc.
2626
- Publishing others’ private information, such as a physical or electronic address, without explicit permission
@@ -47,8 +47,8 @@ Instances of unacceptable behavior can be brought to the attention of the projec
4747

4848
## Consequences
4949

50-
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 and/or UCAR’s Office of Diversity, Equity and Inclusion (ODEI), as well as a participant’s home institution and/or law enforcement. In the event an incident is reported to UCAR, UCAR will follow its Harassment Reporting and Complaint Procedure.
50+
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 a participant’s home institution and/or law enforcement. In the event an incident is reported to UCAR, UCAR will follow its Harassment Reporting and Complaint Procedure.
5151

5252
## Attribution
5353

54-
This Code of Conduct was originally adapted from the Contributor Covenant, version 1.4. We then aligned it with the UCAR Participant Code of Conduct, which also borrows from the American Geophysical Union (AGU) Code of Conduct. The UCAR Participant Code of Conduct applies to both UCAR employees as well as participants in activities run by UCAR. The original version of this for all software projects that have strong management from UCAR or UCAR staff is available on the UCAR website at [https://doi.org/10.5065/6w2c-a132](https://doi.org/10.5065/6w2c-a132). The date that it was adopted by this project was 13 May 2024. When responding to complaints, UCAR HR and ODEI will do so based on the latest published version. Therefore, any project-specific changes should follow the Process for Changes section above.
54+
This Code of Conduct was originally adapted from the Contributor Covenant, version 1.4. We then aligned it with the UCAR Participant Code of Conduct, which also borrows from the American Geophysical Union (AGU) Code of Conduct. The UCAR Participant Code of Conduct applies to both UCAR employees as well as participants in activities run by UCAR. The original version of this for all software projects that have strong management from UCAR or UCAR staff is available on the UCAR website at [https://doi.org/10.5065/6w2c-a132](https://doi.org/10.5065/6w2c-a132). The date that it was adopted by this project was 13 May 2024. When responding to complaints, UCAR HR will do so based on the latest published version. Therefore, any project-specific changes should follow the Process for Changes section above.

0 commit comments

Comments
 (0)