Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
gh-37054:
CODE_OF_CONDUCT.md
: Do not send people to sage-flame
<!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes #1234" use "Introduce new method to calculate 1+1" --> <!-- Describe your changes here in detail --> Facts: - The only place where sage-flame is mentioned is at the bottom of the Code of Conduct, moved from the Sage wiki to the repository in Apr 2022 in #33565 (this PR has pointers to the discussions that established the Code in 2014, including the role of sage-flame) - Moving discussions to sage-flame is the *only* sanction that is mentioned in the Code of Conduct. - The sage-flame list/group has not seen a use after 2019. Here we remove the mention of sage-flame from the Code of Conduct; not only because it has fallen out of actual use, but also because it is harmful: - It is the only sanction mentioned in CoC, and it paints the picture of symmetric behavior: two or more participants engage in a "heated discussion". - Hence it ignores the asymmetric nature of abuse: There is an abuser, and there is a target of the abuse. - Sending both to sage-flame is inappropriate and harmful, as it effectively downplays and legitimizes the conduct of the abuser. References: - https://www.shrm.org/topics-tools/news/managing-smart/damage-done- dealing-narcissists-workplace - https://edib.harvard.edu/calling-and-calling-out-guide <!-- Why is this change required? What problem does it solve? --> <!-- If this PR resolves an open issue, please link to it here. For example "Fixes #12345". --> <!-- If your change requires a documentation PR, please link it appropriately. --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> <!-- Feel free to remove irrelevant items. --> - [ ] The title is concise, informative, and self-explanatory. - [ ] The description explains in detail what this PR is about. - [ ] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on - #12345: short description why this is a dependency - #34567: ... --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> URL: #37054 Reported by: Matthias Köppe Reviewer(s): roed314
- Loading branch information