open-slopware/CODE_OF_CONDUCT.md
2026-07-16 15:47:54 +02:00

9.1 KiB

Official Code of Conduct

No Bigotry

  • No racism.
  • No xenophobia.
  • No colorism/featurism.
  • No casteism.
  • No transphobia.
  • No homophobia/queerphobia.
  • No sexism.
  • No ableism.
  • No islamophobia, antisemitism, or hatred to anyone based on their religion or lack thereof.
  • No classism.
  • No fascism.

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.

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).

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:

<details>
  <summary>Content warning: Homophobia</summary>
  homophobic content goes here.
</details>

That will display like this:

Content warning: Homophobia homophobic content goes here.

Failure to do so will first result in a one time warning and future offenses will be considered a strike. We ask that you do not use the acronym "NSFW" and instead use specific tags such as "nudity" or "discussion of sex" as to be inclusive to all workers.

No CSAM

We do not allow any form of CSAM (and niether does codeberg.org's TOS). Although codeberg does not explicitly note it, we are including a ban on drawn/computer generated CSAM: lolicon, shotacon, or "cub" content. Do not submit tainted software OR alternatives that feature sexualized children (including teenagers) anywhere in the source code, including links to CSAM websites or screenshots.

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.

Handling inappropriate comments

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.

Enforcement

warnings: You made a sarcastic or aggressive comment attacking another user here or elsewhere, regardless of which side you are on. You will get a reminder that you need to be kind here and if you need a comment by another user addressed, you must tag an admin. This warning and any warnings after it are optional and may be skipped if you are doing something that falls into the No Bigotry rules, or if you are clearly operating in bad faith.

We may issue a single strike in instances where we think you may be receptive to being better, but we will not tolerate additional offenses.

Warning

If you are caught being excessively rude here, especially if you're displaying a form of severe bigotry or bringing an inappropriate tone, we reserve the right to ban you from the repo with no strikes and if necessary, we will report you to codeberg.org.

We do not allow people to debate strikes or bans either for themselves or on behalf of others.

Be kind or be gone

  • Do NOT use this repo as a witch hunting device in any direction. You may not reach out on repos, forums, social media, reddit, messaging apps, etc, especially not in a rude way, to maintainers of other repos to harass them and threaten them, especially not with this list. Doing so will result in a ban.

  • Do NOT mention this list at all when reaching out to a project to discuss AI in any way. It only results in putting the maintainers of that project on the defensive, and then the maintainers of this repo need to deal with the fallout of that. If you need help with asking for a No AI Policy, consider checking out our No AI Request Template doc. You are also free to copy and paste anything from the Why not LLMs file.

  • We don't want drive by sarcastic comments.

  • No references to bodily fluids (vomit, urine, feces), this includes emojis. It's gross and unproductive.

  • We don't want people talking about how they never liked a particular piece of software because they didn't like the features.

  • We don't want anyone personally attacking anyone from this repo or other repos.

  • We will delete off-topic comments that have rude vibes or are encouraging a generally rage-feedback atmosphere.

  • This repo is not a substitute for social media. The maintainers do not have the mental health bandwidth to manage such a community.

  • Please do not reach out to the maintainers or collaborators of this repo anywhere but this repo specifically (unless they have given explicit permission to do so). We do not operate our personal email or fediverse accounts as extensions of this repo and will not take feedback there. We need a proper work life balance. Please respect that.

  • No complaining about purity rules, "walking on egg shells", etc. If you can't behave professionally here, then please just kindly exit.

This repo is specifically meant for identifying LLM usage in other projects, and coordinating on alternatives. You can also come here to ask others to please help you in chatting with another repo maintainer to sway them away from AI usage. But you need to do all of it with kindness. We have no interest in a rage feedback atmosphere here and won't tolerate it. Please consider your words before you hit send.

Inclusive Language

Please also keep your language inclusive. To learn more about why this matters, especially with regards to teminology such as "master" or "blacklist", please checkout this draft IETF RFC: Terminology, Power, and Inclusive Language in Internet-Drafts and RFCs.

Gender Neutral Language

When referring to the people who work on this repo, please use gender neutral language unless you are referring to a specific person who you know the pronouns of. You should prefer to use "they/them/themself/themselves" if you do not know the pronouns of the person you're talking to/about. You can learn more about gender neutral language in the following resources:

Some example nouns you can use if you don't know the gender of someone:

  • maintainer
  • collaborator
  • author
  • user
  • colleague
  • friend
  • acquaintance

Tip

Many people put their pronouns in their profile. If you're unsure, you can check there, and if a person has pronouns listed, use those. If there's no pronouns listed, still default to neutral language as mentioned above.

Accessibility

Alt Text

Please provide alt text descriptions for any images you post. This is so that users that are blind or low vision know what is being posted as their screenreaders can read it aloud. This is also useful for people who speak other languages so that they can translate any text from the screenshot and understand context. If you don't provide alt text after being asked to, we will count that as a warning, and if you still fail to do so, it will be a strike. We make exceptions if you yourself have a disability preventing you from doing so. Please kindly ask that someone else provide alt text for you, and when they do, please update your image's alt text. (You do not need to disclose your disability. It is fine to ask others to provide alt text for you for ANY reason.)

Code blocks

Please use syntax highlighting when posting code blocks.