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
* Moving content directory out of way to make copy
* Save copy of content directory
* Restoring original content directory
* Add local theme to repo (much easier to dev)
* Change case of section titles
* Update extensions location and remove comm gallery
* Update and move out of pages
* Update ignores related to move
* Update ignores
* Update index
* Updated makefiles
* Updating images for new theme
* Explicitly add pythia extension
* Update pages and content for new theme
* Update Sphinx config for new theme
* Remove explicit custom.js load (done in extension)
* Add links to gallery
* Formatting only
* For model displays in new theme
* Change name of gallery and affiliation link
* Remove subtitle
* Add HTML logo usage
* Add HTML logo setting and fix img locations
* Fix references with pathto
* Logo and title
* Fix dropdowns to use BS5
* Hide gallery (and some tweaks)
* Gallery formatting
* Rename links to gallery
* New images
* New landing page content
* Match navbar items to new content
* Move custom styling/JS to pythia theme
* Update names in CI
* Point RTD to new portal
* Fix about link
* Fix linting
* Replace divs with sections when appropriate
* Return soup object
* Support div.section and section
* Add extension to dropdown option urls
* Add Code of Conduct button
* Fix link in COC
* Fix copyright flex issue in footer
* Fix button layout
* Add latest contributing to new portal
* Fix prettier ugliness that breaks pre tags
* Admonition styling
* Add seealso admonition
* Move gallery styling/js to custom files
* Attempt a wide-card gallery style
Copy file name to clipboardExpand all lines: CODEOFCONDUCT.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# Code of Conduct
2
2
3
-
## OUR PLEDGE
3
+
## Our Pledge
4
4
5
5
We, as contributors, creators, stewards, and maintainers (participants), of Project Pythia 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.
6
6
7
-
## OUR STANDARDS
7
+
## Our Standards
8
8
9
9
Examples of behaviors that contribute to a positive environment include:
10
10
@@ -29,26 +29,26 @@ Examples of unacceptable behavior include, but are not limited to:
29
29
- Threatening or stalking anyone, including a participant
30
30
- Other conduct which could reasonably be considered inappropriate in a professional setting
31
31
32
-
## SCOPE
32
+
## Scope of this Code
33
33
34
34
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.
35
35
36
-
## COMMUNITY RESPONSIBILITIES
36
+
## Community Responsibilities
37
37
38
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.
39
39
40
-
## PROJECT ADMINISTRATOR RESPONSIBILITIES
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
-
## REPORTING
44
+
## Reporting
45
45
46
46
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 section below.
47
47
48
-
## CONSEQUENCES
48
+
## Consequences
49
49
50
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.
51
51
52
-
## ATTRIBUTION
52
+
## Attribution
53
53
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. The date that it was adopted by this project was 20 December 2020. 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 20 December 2020. 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.
0 commit comments