Skip to content

Commit

Permalink
Update CODE_OF_CONDUCT.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ekluzek authored Dec 18, 2018
1 parent cbeeb88 commit 872d9dc
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Upon receipt of a complaint, the project administrator(s) may take any action de
## 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, email addresses, adoption date, etc. There is one section below marked “optional” that may not apply to a given project.

Projects that adopt this Code of Conduct need to stay up to date with UCAR’s Participant Code of Conduct, linked above. Projects can make limited substantive changes to the Code of Conduct, however, the changes must be limited in scope and may not contradict the Participant Code of Conduct. Substantive changes must be submitted to HR for approval prior to posting.
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" 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, version 1.4, available at [Contributor-Covenant](http://contributor-covenant.org/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. We modified the “scope” section with the django project description, and we added “Publication Ethics” from the NGEET/FATES project. 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 _**`[Enter DOI link name]`**_ (the date that it was adopted by this project was Dec/5/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 section above.
Expand Down

0 comments on commit 872d9dc

Please sign in to comment.