add managing conflict guide #51
Conversation
✅ Deploy Preview for learn-scientific-python-org ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
I really like this!
For managing conflict do we want to recommend that projects include decision-making details in their governance also? Sometimes conflict arises based on technical decision making and ultimately the project needs to make a decision to move forward. Many projects have a consensus-seeking model, but explicitly having a path forward can help individuals move forwards too.
For the CoC violations I think we're covering important basics. Do we also want to include information on community notifications (that is, that the project documents the violation and the resolution path?), anonymous reporting guidelines, and other practices?
| them. | ||
|
|
||
| ### Assume positive intent and acknowledge | ||
| negative impact |
There was a problem hiding this comment.
I think this needs to be moved up to the line above or you need to add the markdown header format for this to continue.
| When the Code of Conduct is violated, you should | ||
| take disciplinary action as detailed therein and | ||
| communicate to the offending party what they did | ||
| wrong and why. Assure the offended party that you | ||
| are taking the offense seriously and detail what | ||
| actions you took to remedy the situation, as well | ||
| as taking into account what their desired outcome | ||
| is. |
There was a problem hiding this comment.
For CoC violations do we want to be explicit about protecting the identity of the reporter also?
| Do not wait for a report to take action on a Code | ||
| of Conduct violation, it's best to address obvious | ||
| breaches of the Code in a timely manner to | ||
| demonstrate that it is important and a priority of | ||
| your project. Staying proactive helps to cultivate |
There was a problem hiding this comment.
I love that you added this! Emphasizing timeliness is definitely something we want.
Co-authored-by: Madicken Munk <[email protected]>
jarrodmillman
force-pushed
the
managing-conflict
branch
from
f6ec5d3 to
f40fb27
Compare
No description provided.