Skip to content

Commit 92beecd

Browse files
committed
Add code of conduct
Signed-off-by: Sylvain Hellegouarch <sh@defuze.org>
1 parent e23fa6c commit 92beecd

File tree

1 file changed

+71
-0
lines changed

1 file changed

+71
-0
lines changed

CODE_OF_CONDUCT.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
# Chaos Toolkit Code Of Conduct
2+
3+
Chaos Toolkit adopts Debian project's Code Of Conduct for its
4+
participants and contributors.
5+
6+
## Be respectful
7+
8+
In the Chaos Toolkit project, inevitably there will be people with whom you
9+
may disagree, or find it difficult to cooperate. Accept that, but even
10+
so, remain respectful. Disagreement is no excuse for poor behaviour or
11+
personal attacks, and a community in which people feel threatened is
12+
not a healthy community.
13+
14+
## Assume good faith
15+
16+
Chaos Toolkit contributors have many ways of reaching our common goal
17+
of an open API for Chaos Engineering which may differ from your
18+
ways. Assume that other people are working towards this goal.
19+
20+
Note that many of our Contributors are from around the globe, not
21+
native English speakers and may have different cultural backgrounds.
22+
23+
## Be Collaborative
24+
25+
Chaos Toolkit is a large project; there is always more to learn within
26+
it. It's good to ask for help when you need it. Similarly, offers for
27+
help should be seen in the context of our shared goal of improving
28+
Chaos Toolkit.
29+
30+
When you make something for the benefit of the project, be willing to
31+
explain to others how it works, so that they can build on your work to
32+
make it even better.
33+
34+
## Try to be concise
35+
36+
Keep in mind that what you write once will be read by hundreds of
37+
people. Writing a short email means people can understand the
38+
conversation as efficiently as possible. When a long explanation is
39+
necessary, consider adding a summary.
40+
41+
Try to bring new arguments to a conversation so that each mail adds
42+
something unique to the thread, keeping in mind that the rest of the
43+
thread still contains the other messages with arguments that have
44+
already been made.
45+
46+
Try to stay on topic, especially in discussions that are already fairly large.
47+
48+
## Be open
49+
50+
Most ways of communication used within Chaos Toolkit allow for public
51+
and private communication. You should use public methods of
52+
communication for Chaos Toolkit related messages, unless posting
53+
something sensitive.
54+
55+
## In case of problems
56+
57+
While this code of conduct should be adhered to by participants, we
58+
recognize that sometimes people may have a bad day, or be unaware of
59+
some of the guidelines in this code of conduct. When that happens, you
60+
may reply to them and point out this code of conduct. Instances of
61+
otherwise unacceptable behavior may be reported by contacting team at
62+
contact@chaostoolkit.org. All complaints will be reviewed and
63+
investigated and will result in a response that is appropriate to the
64+
circumstances.
65+
66+
67+
## Attribution
68+
69+
This Code of Conduct is adapted from the [Debian Code Of Conduct][homepage], version 1.0
70+
71+
[homepage]: https://www.debian.org/code_of_conduct

0 commit comments

Comments
 (0)