Skip to content

Commit e68420e

Browse files
authored
Add a code of conduct (uber-go#486)
Add the Contributor Covenant, with [email protected] as the contact email.
1 parent f948727 commit e68420e

File tree

4 files changed

+98
-1
lines changed

4 files changed

+98
-1
lines changed

.readme.tmpl

+10
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,16 @@ All APIs are finalized, and no breaking changes will be made in the 1.x series
8080
of releases. Users of semver-aware dependency management systems should pin
8181
zap to `^1`.
8282

83+
## Contributing
84+
85+
We encourage and support an active, healthy community of contributors —
86+
including you! Details are in the [contribution guide](CONTRIBUTING.md) and
87+
the [code of conduct](CODE_OF_CONDUCT.md). The zap maintainers keep an eye on
88+
issues and pull requests, but you can also report any negative conduct to
89+
[email protected]. That email list is a private, safe space; even the zap
90+
maintainers don't have access, so don't hesitate to hold us to a high
91+
standard.
92+
8393
<hr>
8494

8595
Released under the [MIT License](LICENSE.txt).

CODE_OF_CONDUCT.md

+75
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age,
8+
body size, disability, ethnicity, gender identity and expression, level of
9+
experience, nationality, personal appearance, race, religion, or sexual
10+
identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an
52+
appointed representative at an online or offline event. Representation of a
53+
project may be further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [email protected]. The project
59+
team will review and investigate all complaints, and will respond in a way
60+
that it deems appropriate to the circumstances. The project team is obligated
61+
to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
71+
version 1.4, available at
72+
[http://contributor-covenant.org/version/1/4][version].
73+
74+
[homepage]: http://contributor-covenant.org
75+
[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,9 @@ We'd love your help making zap the very best structured logging library in Go!
44

55
If you'd like to add new exported APIs, please [open an issue][open-issue]
66
describing your proposal &mdash; discussing API changes ahead of time makes
7-
pull request review much smoother.
7+
pull request review much smoother. In your issue, pull request, and any other
8+
communications, please remember to treat your fellow contributors with
9+
respect! We take our [code of conduct](CODE_OF_CONDUCT.md) seriously.
810

911
Note that you'll need to sign [Uber's Contributor License Agreement][cla]
1012
before we can accept any of your contributions. If necessary, a bot will remind

README.md

+10
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,16 @@ All APIs are finalized, and no breaking changes will be made in the 1.x series
108108
of releases. Users of semver-aware dependency management systems should pin
109109
zap to `^1`.
110110

111+
## Contributing
112+
113+
We encourage and support an active, healthy community of contributors &mdash;
114+
including you! Details are in the [contribution guide](CONTRIBUTING.md) and
115+
the [code of conduct](CODE_OF_CONDUCT.md). The zap maintainers keep an eye on
116+
issues and pull requests, but you can also report any negative conduct to
117+
[email protected]. That email list is a private, safe space; even the zap
118+
maintainers don't have access, so don't hesitate to hold us to a high
119+
standard.
120+
111121
<hr>
112122

113123
Released under the [MIT License](LICENSE.txt).

0 commit comments

Comments
 (0)