Skip to content

Commit 80eb5b9

Browse files
author
Bill Ladwig
committed
Merge branch 'release/1.3.2.1'
2 parents 5682aa5 + d1f40ce commit 80eb5b9

File tree

20 files changed

+1883
-32
lines changed

20 files changed

+1883
-32
lines changed

.circleci/config.yml

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,23 @@
44
#
55
version: 2
66
jobs:
7+
lint:
8+
docker:
9+
- image: circleci/python:3.6.1
10+
11+
working_directory: ~/repo
12+
13+
steps:
14+
- checkout
15+
- run:
16+
name: install pycodestyle
17+
command: |
18+
sudo pip install pycodestyle
19+
- run:
20+
name: run pycodestyle
21+
command: |
22+
pycodestyle src test
23+
724
build:
825
docker:
926
# specify the version you desire here
@@ -74,3 +91,9 @@ jobs:
7491
- store_artifacts:
7592
path: test-reports
7693
destination: test-reports
94+
workflows:
95+
version: 2
96+
build_and_lint:
97+
jobs:
98+
- build
99+
- lint

CODE_OF_CONDUCT.md

Lines changed: 182 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,182 @@
1+
# Contributor Code of Conduct
2+
3+
## Related Code of Conduct
4+
5+
Participant Code of Conduct
6+
[https://www2.fin.ucar.edu/ethics/participant-code-conduct](https://www2.fin.ucar.edu/ethics/participant-code-conduct)
7+
8+
## Our Pledge
9+
10+
We, as contributors and maintainers (participants), of WRF-Python pledge to
11+
make participation in our software project and community a safe, productive,
12+
welcoming and inclusive experience for everyone. All participants are required
13+
to abide by this Code of Conduct. This includes respectful treatment of
14+
everyone regardless of age, body size, disability, ethnicity, gender identity
15+
or expression, level of experience, nationality, political affiliation,
16+
veteran status, pregnancy, genetic information, physical appearance, race,
17+
religion, or sexual orientation, as well as any other characteristic protected
18+
under applicable US federal or state law.
19+
20+
## Our Standards
21+
22+
Examples of behaviors that contribute to a positive environment include:
23+
24+
* Using welcoming and inclusive language
25+
* Respectful when offering and gracefully accepting constructive criticism
26+
* Acknowledging the contributions of others
27+
* Focusing on what is best for the community
28+
* Showing empathy towards other community members
29+
* Treating everyone with respect and consideration, valuing a diversity of
30+
views and opinions
31+
* Communicating openly with respect for others, critiquing ideas rather than
32+
individuals
33+
34+
Examples of unacceptable behavior include, but are not limited to:
35+
36+
* Harassment, intimidation, or discrimination in any form
37+
* Personal attacks directed toward other participants
38+
* Unwelcome sexual attention or advances
39+
* Inappropriate, negative, derogatory comments and/or attacks on personal
40+
beliefs
41+
* Publishing others' private information, such as a physical or electronic
42+
address, without explicit permission
43+
* Refusing to use the pronouns that someone requests
44+
* Alarming, intimidating, threatening, or hostile comments or conduct
45+
* Physical or verbal abuse by anyone to anyone, including but not limited to a
46+
participant, member of the public, guest, member of any institution or
47+
sponsor
48+
* Comments related to characteristics given in the pledge at the top
49+
* Inappropriate use of nudity and/or sexual images
50+
* Threatening or stalking other participants
51+
* Other conduct which could reasonably be considered inappropriate in a
52+
professional setting
53+
54+
## Scope
55+
56+
This Code of Conduct applies to all spaces managed by the Project whether it
57+
be online or face-to-face. This includes project code, code repository,
58+
associated web pages, documentation, mailing lists, project websites and
59+
wiki pages, issue tracker, meetings, telecons, events, project social media
60+
accounts, and any other forums created by the project team which the community
61+
uses for communication. In addition, violations of this Code of Conduct
62+
outside these spaces may affect a person's ability to participate within them.
63+
Representation of a project may be further defined and clarified by project
64+
maintainers.
65+
66+
## Community Responsibilities
67+
68+
Everyone in the community is empowered to respond to people who are showing
69+
unacceptable behavior. They can talk to them privately or publicly. Anyone
70+
requested to stop unacceptable behavior is expected to comply immediately.
71+
If the behavior continues concerns may be brought to the project
72+
administrators or to any other party listed in the Reporting section below.
73+
74+
## Project Administrator Responsibilities
75+
76+
Project Administrators are responsible for clarifying the standards of
77+
acceptable behavior and are encouraged to model appropriate behavior and
78+
provide support when people in the community point out inappropriate behavior.
79+
Project administrator(s) are normally the ones that would be tasked to carry
80+
out the actions in the Consequences section below.
81+
82+
Project Administrators are also expected to keep this Code of Conduct updated
83+
with the main one housed at UCAR as listed below in the Attribution section.
84+
85+
## Reporting
86+
87+
Instances of unacceptable behavior can be brought to the attention of the
88+
project administrator(s) who may take any action as outlined in the
89+
Consequences section below. However, making a report to a project
90+
administrator is not considered an 'official report' to UCAR.
91+
92+
Instances of unacceptable behavior may also be reported directly to UCAR via
93+
UCAR's Harassment Reporting and Complaint Procedure at [https://www2.fin.ucar.edu/procedures/hr/harassment-reporting-and-complaint-procedure](https://www2.fin.ucar.edu/procedures/hr/harassment-reporting-and-complaint-procedure),
94+
or anonymously through UCAR's EthicsPoint Hotline at [https://www2.fin.ucar.edu/ethics/anonymous-reporting](https://www2.fin.ucar.edu/ethics/anonymous-reporting).
95+
96+
Complaints received by UCAR will be handled pursuant to the procedures
97+
outlined in UCAR's Harassment Reporting and Complaint Procedure. Complaints
98+
to UCAR will be held as confidential as practicable under the circumstances,
99+
and retaliation against a person who initiates a complaint or an inquiry about
100+
inappropriate behavior will not be tolerated.
101+
102+
Any Contributor can use these reporting methods even if they are not directly
103+
affiliated with UCAR. The Frequently Asked Questions (FAQ) page for reporting
104+
is here: [https://www2.fin.ucar.edu/procedures/hr/reporting-faqs](https://www2.fin.ucar.edu/procedures/hr/reporting-faqs).
105+
106+
## Consequences
107+
108+
Upon receipt of a complaint, the project administrator(s) may take any action
109+
deemed necessary and appropriate under the circumstances. Such action can
110+
include things such as: removing, editing, or rejecting comments, commits,
111+
code, wiki edits, email, issues, and other contributions that are not aligned
112+
to this Code of Conduct, or banning temporarily or permanently any contributor
113+
for other behaviors that are deemed inappropriate, threatening, offensive, or
114+
harmful. Project Administrators also have the right to report violations to
115+
UCAR HR and/or UCAR's Office of Diversity, Equity and Inclusion (ODEI) as
116+
well as a participant's home institution and/or law enforcement. In the event
117+
an incident is reported to UCAR, UCAR will follow its Harassment Reporting
118+
and Complaint Procedure.
119+
120+
## Process for Changes
121+
122+
All UCAR managed projects are required to adopt this Contributor Code of
123+
Conduct. Adoption is assumed even if not expressly stated in the repository.
124+
Projects should fill in sections where prompted with project-specific
125+
information, including, project name, email addresses, adoption date, etc.
126+
There is one section below marked "optional" that may not apply to a given
127+
project.
128+
129+
Projects that adopt this Code of Conduct need to stay up to date with
130+
UCAR's Contributor Code of Conduct, linked with a DOI in the "Attribution"
131+
section below. Projects can make limited substantive changes to the Code of
132+
Conduct, however, the changes must be limited in scope and may not contradict
133+
the UCAR Contributor Code of Conduct.
134+
135+
## Attribution
136+
137+
This Code of Conduct was originally adapted from the Contributor Covenant,
138+
version 1.4, available at [Contributor-Covenant](http://contributor-covenant.org/version/1/4).
139+
We then aligned it with the UCAR Participant Code of Conduct, which also
140+
borrows from the American Geophysical Union (AGU) Code of Conduct. The UCAR
141+
Participant Code of Conduct applies to both UCAR employees as well as
142+
participants in activities run by UCAR. We modified the "scope" section with
143+
the django project description, and we added "Publication Ethics" from
144+
the NGEET/FATES project. The original version of this for all software
145+
projects that have strong management from UCAR or UCAR staff is available
146+
on the UCAR website at [*Enter DOI link name*] (the date that it was adopted
147+
by this project was [*Enter date adopted*]). When responding to complaints
148+
UCAR HR and ODEI will do so based on the latest published version. Therefore,
149+
any project-specific changes should follow the Process for Changes section
150+
above.
151+
152+
## Publication Ethics (optional)
153+
154+
We aim to create an open development environment where developers can be
155+
confident that all members of the community are publishing any research
156+
on the project in an ethical manner. In particular, writing code is a form of
157+
intellectual contribution, and one should expect that all such intellectual
158+
contributions are respected and given credit in any resulting published work.
159+
To support the community and avoid issues of misconduct related to the above
160+
principle, please respect the following rules:
161+
162+
* Document the version of the code used in any publication, preferably by
163+
either using a release tag (existing or newly created) if possible, or a
164+
commit hash if not.
165+
166+
* Do not use code from anywhere other than the central project's development
167+
repository main development branch without discussing with the author(s) of
168+
the modified code your intentions for using the code and receiving their
169+
permission to do so.
170+
171+
* When using project features that have recently been integrated into the
172+
central Project development repository, be mindful of the contributions
173+
of others and, where the novel features qualitatively affect the results,
174+
involve the author(s) of these features in any resulting manuscripts.
175+
Be particularly aware of the concerns of early career researchers, and
176+
ensure they have sufficient time to lead publications using their
177+
developments.
178+
179+
* When discussing results arising from older project features that have been
180+
described in the literature or releases, accurately cite the publications
181+
describing those features or releases.
182+

0 commit comments

Comments
 (0)