remote/open-slopware
1
0
Fork 0
mirror of https://codeberg.org/small-hack/open-slopware.git synced 2026-07-17 00:44:32 +02:00
Code Issues Projects Releases Packages Wiki Activity

clean up titles to be less long

Browse source
This commit is contained in:
ethical-foss-admin 2026-07-16 11:21:24 +00:00
commit 2c1bedd7a5
No known key found for this signature in database
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
CODE_OF_CONDUCT.md
View file

@ -1,9 +1,9 @@
# Official Code of Conduct
* [No Bigotry](#no-bigotry)
* [On handling bigotry or unsavory content for the purposes of the open-slopware list](#on-handling-bigotry-or-unsavory-content-for-the-purposes-of-the-open-slopware-list)
* [Discussion of bigotry or unsavory content](#discussion-of-bigotry-or-unsavory-content)
* [No CSAM](#no-csam)
* [On handling rude comments in this repo specifically](#on-handling-rude-comments-in-this-repo-specifically)
* [Handling inappropriate comments](#handling-inappropriate-comments)
* [Enforcement](#enforcement)
* [Be kind or be gone](#be-kind-or-be-gone)
* [Inclusive Language](#inclusive-language)
@ -28,9 +28,9 @@
When it comes to bigotry, if you're found to have been broken one of the "No Bigotry" rules, you may not participate here. Your software is also disqualified from being listed as an alternative or suggested for the "More Kind Eyes" or "Call for Collaborators" Issue types.
## On handling bigotry or unsavory content for the purposes of the open-slopware list
## Discussion of bigotry or unsavory content
It is still worth bringing up if a core repo maintainer has a history of bigotry such as racism, transphobia, etc, if it's in the context of adding an alternative software or something to that nature, but still just be objective, e.g. "We should not add a link to x because it is maintained by a transphobic person, see evidence here" and just leave it at that. We'll take that feedback and reject a pull request or ask someone to modify it if it's relevant for community safety (like ensuring people avoid software maintained by discriminatory people for instance).
It is still worth bringing up if a core repo maintainer has a history of bigotry such as racism, transphobia, etc, *if it's in the context of adding an alternative software* or something to that nature, but still just be objective, e.g. "We should not add a link to x because it is maintained by a transphobic person, see evidence here" and just leave it at that. We'll take that feedback and reject a pull request or ask someone to modify it if it's relevant for community safety (like ensuring people avoid software maintained by discriminatory people for instance).
If you must link or provide screenshots of something that displays bigotry, gore, or anything sexual in nature, you *must* add a content warning. Content warnings must be specific to the subject matter. Below, we will give you an example on how to do so:
@ -56,9 +56,9 @@ We do not allow any form of CSAM (and niether does codeberg.org's [TOS](https://
If you need to talk about a someone being accused of something related to CSAM in the context of alternatives in this repo, please use a specific Content Warning as described above.
# On handling rude comments in this repo specifically
# Handling inappropriate comments
If you see someone behaving inappropriately, do not feed their behavior. Tag @ethical-foss-admin instead. They will handle it.
If you see someone behaving inappropriately in this repo, do not feed their behavior. Tag @ethical-foss-admin instead. They will handle it.
In some cases, we may delete comments, issues, or PRs if they're encouraging an inappropriate atmosphere e.g. a popular maintainer has come in with an accusatory tone and is actively advertising their followers to come and spam the repo.