108 lines
7.3 KiB
Markdown
108 lines
7.3 KiB
Markdown
# Contributor Code of Conduct
|
|
_The Contributor Code of Conduct is for participants in our software projects and community._
|
|
|
|
## Our Pledge
|
|
We, as contributors, creators, stewards, and maintainers (participants), of **Community Terrestrial Systems Model (CTSM)** pledge to make participation in
|
|
our software, system or hardware project and community a safe, productive, welcoming and inclusive experience for everyone.
|
|
All participants are required to abide by this Code of Conduct.
|
|
This includes respectful treatment of everyone regardless of age, body size, disability, ethnicity, gender identity or expression,
|
|
level of experience, nationality, political affiliation, veteran status, pregnancy, genetic information, physical appearance, race,
|
|
religion, or sexual orientation, as well as any other characteristic protected under applicable US federal or state law.
|
|
|
|
## Our Standards
|
|
Examples of behaviors that contribute to a positive environment include:
|
|
|
|
* All participants are treated with respect and consideration, valuing a diversity of views and opinions
|
|
* Be considerate, respectful, and collaborative
|
|
* Communicate openly with respect for others, critiquing ideas rather than individuals and gracefully accepting criticism
|
|
* Acknowledging the contributions of others
|
|
* Avoid personal attacks directed toward other participants
|
|
* Be mindful of your surroundings and of your fellow participants
|
|
* Alert UCAR staff and suppliers/vendors if you notice a dangerous situation or someone in distress
|
|
* Respect the rules and policies of the project and venue
|
|
|
|
Examples of unacceptable behavior include, but are not limited to:
|
|
|
|
* Harassment, intimidation, or discrimination in any form
|
|
* Physical, verbal, or written abuse by anyone to anyone, including repeated use of pronouns other than those requested
|
|
* Unwelcome sexual attention or advances
|
|
* Personal attacks directed at other guests, members, participants, etc.
|
|
* Publishing others' private information, such as a physical or electronic address, without explicit permission
|
|
* Alarming, intimidating, threatening, or hostile comments or conduct
|
|
* Inappropriate use of nudity and/or sexual images
|
|
* Threatening or stalking anyone, including a participant
|
|
* Other conduct which could reasonably be considered inappropriate in a professional setting
|
|
|
|
## Scope
|
|
This Code of Conduct applies to all spaces managed by the Project whether they be physical, online or face-to-face.
|
|
This includes project code, code repository, associated web pages, documentation, mailing lists, project websites and wiki pages,
|
|
issue tracker, meetings, telecons, events, project social media accounts, and any other forums created by the project team which the
|
|
community uses for communication.
|
|
In addition, violations of this Code of Conduct outside these spaces may affect a person's ability to participate within them.
|
|
Representation of a project may be further defined and clarified by project maintainers.
|
|
|
|
## 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](#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](#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](#attribution) section.
|
|
|
|
## Reporting
|
|
Instances of unacceptable behavior can be brought to the attention of the project administrator(s) who may take any action as
|
|
outlined in the [Consequences](#consequences) section below.
|
|
However, making a report to a project administrator is not considered an 'official report' to UCAR.
|
|
|
|
Instances of unacceptable behavior may also be reported directly to UCAR pursuant to [UCAR's Harassment Reporting and Complaint
|
|
Procedure](https://www2.fin.ucar.edu/procedures/hr/harassment-reporting-and-complaint-procedure), or anonymously through [UCAR's
|
|
EthicsPoint Hotline](https://www2.fin.ucar.edu/ethics/anonymous-reporting).
|
|
|
|
Complaints received by UCAR will be handled pursuant to the procedures outlined in UCAR's Harassment Reporting and Complaint
|
|
Procedure.
|
|
Complaints to UCAR will be held as confidential as practicable under the circumstances, and retaliation against a person who
|
|
initiates a complaint or an inquiry about inappropriate behavior will not be tolerated.
|
|
|
|
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://www2.fin.ucar.edu/procedures/hr/reporting-faqs).
|
|
|
|
## 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 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.
|
|
|
|
## Process for Changes
|
|
All UCAR managed projects are required to adopt this Contributor Code of Conduct.
|
|
Adoption is assumed even if not expressly stated in the repository.
|
|
Projects should fill in sections where prompted with project-specific information, including, project name and adoption date.
|
|
|
|
Projects that adopt this Code of Conduct need to stay up to date with UCAR's Contributor Code of Conduct, linked with a DOI in the
|
|
[Attribution](#attribution) section below.
|
|
Projects can make limited substantive changes to the Code of Conduct, however, the changes must be limited in scope and may not
|
|
contradict the UCAR Contributor Code of Conduct.
|
|
|
|
## Attribution
|
|
This Code of Conduct was originally adapted from the [Contributor Covenant](http://contributor-covenant.org/version/1/4), 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.
|
|
The date that it was adopted by this project was **Feb/13/2018**.
|
|
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](#process-for-changes) section above.
|