Skip to content

Commit b78b245

Browse files
committed
add managing conflict guide
1 parent af0fb9d commit b78b245

File tree

2 files changed

+65
-0
lines changed

2 files changed

+65
-0
lines changed

content/maintainers/_index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,4 +8,7 @@ This is a draft document.
88

99
The scientific Python ecosystem welcomes your expertise and enthusiasm!
1010

11+
- [Managing conflict]({{< relref
12+
"/maintainers/managing_conflict" >}})
1113
- [Project Meetings Guide]({{< relref "/maintainers/meeting_types" >}})
14+
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: "Managing conflict"
3+
---
4+
5+
{{< notice warning >}}
6+
This is a draft document.
7+
{{< /notice >}}
8+
9+
### Code of Conduct
10+
It's a good idea to have a Code of Conduct to hold
11+
your community members accountable to and create a
12+
safe and inclusive space for everyone. This helps
13+
establish clear expectations on how community
14+
members should behave respectfully in their
15+
interactions with each other and serves as a
16+
reference for fair arbitration when the need
17+
arises.
18+
19+
You can base your Code of Conduct off of similar
20+
projects' ones or use the [Contributor
21+
Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md)
22+
as a starting point, tailoring it to your
23+
community's specific needs. Larger projects should
24+
have an impartial committee dedicated to handling
25+
Code of Conduct violations, and a method for
26+
community members to privately raise issues to
27+
them.
28+
29+
### Assume positive intent and acknowledge
30+
negative impact
31+
Many interpersonal conflicts stem from simple
32+
misunderstandings. It is important to assume
33+
positive intent and acknowledge negative impact to
34+
prevent further escalation of the situation.
35+
Remind everyone that they share the same goals and
36+
try to find commonalities between each party's
37+
reasonings. Validate that perhaps the offending
38+
party meant no malice while also validating the
39+
ways that the offended party was hurt.
40+
41+
### When to step in
42+
Once discussions begin to get heated, with
43+
misunderstandings and accusations getting thrown
44+
it, it is best to step in, ask people to cool off,
45+
and try to find a way for them to understand each
46+
other.
47+
48+
When the Code of Conduct is violated, you should
49+
take disciplinary action as detailed therein and
50+
communicate to the offending party what they did
51+
wrong and why. Assure the offended party that you
52+
are taking the offense seriously and detail what
53+
actions you took to remedy the situation, as well
54+
as taking into account what their desired outcome
55+
is.
56+
57+
Do not wait for a report to take action on a Code
58+
of Conduct violation, it's best to address obvious
59+
breaches of the Code in a timely manner to
60+
demonstrate that it is important and a priority of
61+
your project. Staying proactive helps to cultivate
62+
a positive and healthy community dynamic.

0 commit comments

Comments
 (0)