|
| 1 | +# Code of Conduct |
| 2 | + |
| 3 | +## Our Pledge |
| 4 | + |
| 5 | +We, as contributors, creators, stewards, and maintainers (participants), of GeoCAT-viz pledge to make participation in our |
| 6 | +project and community a safe, productive, welcoming and inclusive experience for everyone. All participants are required |
| 7 | +to abide by this Code of Conduct. This includes respectful treatment of everyone regardless of age, body size, disability, |
| 8 | +ethnicity, gender identity or expression, level of experience, nationality, political affiliation, veteran status, pregnancy, |
| 9 | +genetic information, physical appearance, race, religion, or sexual orientation, as well as any other characteristic protected |
| 10 | +under applicable US federal or state law. |
| 11 | + |
| 12 | +## Our Standards |
| 13 | + |
| 14 | +Examples of behaviors that contribute to a positive environment include: |
| 15 | + |
| 16 | +- All participants are treated with respect and consideration, valuing a diversity of views and opinions |
| 17 | +- Be considerate, respectful, and collaborative |
| 18 | +- Communicate openly with respect for others, critiquing ideas rather than individuals and gracefully accepting criticism |
| 19 | +- Acknowledging the contributions of others |
| 20 | +- Avoid personal attacks directed toward other participants |
| 21 | +- Be mindful of your surroundings and of your fellow participants |
| 22 | +- Alert project administrators if you notice a dangerous situation or someone in distress |
| 23 | +- Respect the rules and policies of the project and venue |
| 24 | + |
| 25 | +Examples of unacceptable behavior include, but are not limited to: |
| 26 | + |
| 27 | +- Harassment, intimidation, or discrimination in any form |
| 28 | +- Physical, verbal, or written abuse by anyone to anyone, including repeated use of pronouns other than those requested |
| 29 | +- Unwelcome sexual attention or advances |
| 30 | +- Personal attacks directed at other guests, members, participants, etc. |
| 31 | +- Publishing others’ private information, such as a physical or electronic address, without explicit permission |
| 32 | +- Alarming, intimidating, threatening, or hostile comments or conduct |
| 33 | +- Inappropriate use of nudity and/or sexual images |
| 34 | +- Threatening or stalking anyone, including a participant |
| 35 | +- Other conduct which could reasonably be considered inappropriate in a professional setting |
| 36 | + |
| 37 | +## Scope |
| 38 | + |
| 39 | +This Code of Conduct applies to all spaces managed by GeoCAT whether they be physical, online or face-to-face. |
| 40 | +This includes project code, code repository, associated web pages, documentation, mailing lists, project websites |
| 41 | +and wiki pages, issue tracker, meetings, telecons, events, project social media accounts, and any other forums |
| 42 | +created by the project team which the community uses for communication. In addition, violations of this Code of |
| 43 | +Conduct outside these spaces may affect a person's ability to participate within them. Representation of a project |
| 44 | +may be further defined and clarified by project maintainers. |
| 45 | + |
| 46 | +## Community Responsibilities |
| 47 | + |
| 48 | +Everyone in the community is empowered to respond to people who are showing unacceptable behavior. They can talk to |
| 49 | +them privately or publicly. Anyone requested to stop unacceptable behavior is expected to comply immediately. If the |
| 50 | +behavior continues concerns may be brought to the project administrators or to any other party listed in the Reporting |
| 51 | +section below. |
| 52 | + |
| 53 | +## Project Administrator Responsibilities |
| 54 | + |
| 55 | +Project administrators are responsible for clarifying the standards of acceptable behavior and are encouraged to model |
| 56 | +appropriate behavior and provide support when people in the community point out inappropriate behavior. Project |
| 57 | +administrator(s) are normally the ones that would be tasked to carry out the actions in the Consequences section below. |
| 58 | + |
| 59 | +## Reporting |
| 60 | + |
| 61 | +Instances of unacceptable behavior can be brought to the attention of the project administrator(s) who may take any action |
| 62 | +as outlined in the Consequences section below. However, making a report to a project administrator is not considered an |
| 63 | +‘official report’ to UCAR. |
| 64 | + |
| 65 | +## Consequences |
| 66 | + |
| 67 | +Upon receipt of a complaint, the project administrator(s) may take any action deemed necessary and appropriate under the |
| 68 | +circumstances. Such action can include things such as: removing, editing, or rejecting comments, commits, code, wiki edits, |
| 69 | +email, issues, and other contributions that are not aligned to this Code of Conduct, or banning temporarily or permanently |
| 70 | +any contributor for other behaviors that are deemed inappropriate, threatening, offensive, or harmful. Project administrators |
| 71 | +also have the right to report violations to UCAR HR and/or UCAR’s Office of Diversity, Equity and Inclusion (ODEI), as well |
| 72 | +as a participant’s home institution and/or law enforcement. In the event an incident is reported to UCAR, UCAR will follow |
| 73 | +its Harassment Reporting and Complaint Procedure. |
| 74 | + |
| 75 | +## Attribution |
| 76 | + |
| 77 | +This Code of Conduct was originally adapted from the Contributor Covenant, version 1.4. We then aligned it with the UCAR |
| 78 | +Participant Code of Conduct, which also borrows from the American Geophysical Union (AGU) Code of Conduct. The UCAR Participant |
| 79 | +Code of Conduct applies to both UCAR employees as well as participants in activities run by UCAR. The original version of this |
| 80 | +for all software projects that have strong management from UCAR or UCAR staff is available on the UCAR website at |
| 81 | +[https://doi.org/10.5065/6w2c-a132](https://doi.org/10.5065/6w2c-a132). The date that it was adopted by this project was 2 |
| 82 | +October 2023. When responding to complaints, UCAR HR and ODEI will do so based on the latest published version. |
0 commit comments