Merge lp:~jelmer/brz/code-of-conduct into lp:brz/3.1

Proposed by Jelmer Vernooij
Status: Merged
Approved by: Jelmer Vernooij
Approved revision: no longer in the source branch.
Merge reported by: The Breezy Bot
Merged at revision: not available
Proposed branch: lp:~jelmer/brz/code-of-conduct
Merge into: lp:brz/3.1
Diff against target: 80 lines (+76/-0)
1 file modified
CODE_OF_CONDUCT.md (+76/-0)
To merge this branch: bzr merge lp:~jelmer/brz/code-of-conduct
Reviewer Review Type Date Requested Status
Martin Packman Approve
Review via email: mp+386850@code.launchpad.net

Commit message

Add a code of conduct.

Description of the change

Add a code of conduct.

This is the Contributor Covenant Code of Conduct from
https://www.contributor-covenant.org/, used by e.g. Linux and Git.

To post a comment you must log in.
Revision history for this message
Martin Packman (gz) wrote :

Seems reasonable. I could quibble about unenumerated rights but it makes sense to adopt something reasonably commonly used as is.

review: Approve

Preview Diff

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

Subscribers

People subscribed via source and target branches