open-slopware/CONTRIBUTING.md

Warning

Before you interact with this repo, please read the Code of Conduct! This is a repo for nice people only! We would also appreciate it if you did not mention this repo on social media or in chats in order to shame a project or community. Do not make posts like, "<project> should be added to the open-slopware list", especially if you are tagging a maintainer or using a project's hashtag.

Contributing Pull Requests

For Adding or Updating Tainted Software

To contribute to this list, file a pull request adding it to the appropriate category, along with any known alternatives. The pull request must include links to evidence (see Criteria).

Title the pull request one of the following:

• Add <software-name>
• Add <software-name> as an Alternative for <software-name>
• Add <software-name> as an Alternative for <category>
• Update <software-name>

Important

Please do your best to research alternatives to the slopware before submitting a PR. It's important to elevate projects that aren't drinking the slop so we don't all lose hope <3

Please make sure to only submit a PR for 1 section at a time, otherwise it is more difficult to coordinate between multiple Issues and PRs.

Other tips for keeping the repo tidy and making sure we don't duplicate efforts:

• Search for the software name in the Issues and Pull Requests of this repo. (Great minds think alike ❤️)
  • If the software is already reported in an open Issue, but not as a PR, open your PR linking to the open issue with the following description, so the related issue gets automatically closed if the PR gets merged:

    - Closes #123
    

• If the software is already reported in an open issue and as an open PR leave a comment in the PR with the new or updated evidence(s).
• When submitting a PR, make sure you're comfortable with the description of the PR being what gets committed. We use the PR description when squashing all commits before merging. We default to sqaushing and merging, so that if the repo has only one commit per PR.

Note

Don't know how to create a PR? You can learn more about that in the Codeberg Pull Requests and Git Flow docs 🩵

Criteria

The criteria for being included in this repository are any of following tags. You can click each one to jump to the definition and acceptable evidence:

• (only to be used in extreme cases)
• 
• 
• 
• 
• 
• 
• 
• 

Alternatives should not contain any slop as defined by our tagging system above.

Please don't submit social media posts as evidence unless it is a post by a maintainer of the tainted project talking about using AI to develop the tainted project. Even then, we'd prefer links to a project's LLM commits in a git forge, AI/contributing policies, or blog posts.

Style guide

When submitting new software to this list, please check out the style guide to ensure you are conforming to our community agreed upon standards.

Removal of "Tainted" Status

Any project here may have the "Tainted" status removed as long as the following become true, even if prior LLM-authored code remains:

1. The project establishes a "No genAI" policy, where the core developers commit to no longer using LLMs for developing that project in particular and no longer accepting obvious LLM-authored contributions, and state the policy prominently in their repo.
2. Any genAI functionality of the project itself is removed in its entirety. "Kill switches" are insufficient.
3. Any LLM friendly files/folders are either poisoned or removed entirely.

Title the pull request like this:

Remove <software-name>

When submitting a project for removal, please include a link to the evidence that they have created a "No genAI" policy. You can also submit PRs to update if a project stops using something like , but keeps a . Updates are always welcome.

Do you see a project on this list that you wish was not on it? Please consider reaching out in a kind way to suggest they implement a No AI Policy. You can check out our No AI Request Template for inspiration 🙏

Note

Age of evidence is not grounds for removal. Example: If agent instructions were added several years ago, but have never been removed, this evidence is still valid and the only way to have the project's tainted status removed is for them to remove those instructions and to put out a No AI policy. We do not make exceptions to this rule.

Adding Alternatives to Tainted Software

Feel free to submit any software as an alternative provided it is FOSS, has no AI in the code base, and is not associated with hate or bigotry (see examples of bigotry. You can absolute self-submit

Unqualified Alternatives

• Any project associated with bigotry is not allowed.

• At this time, we're not accepting alternatives that are centralized and/or lacking the appropriate documentation to be self-hosted by non-experts. For example, we will not endorse the messaging app "Signal", or social media platforms based on AT-protocol. In the event that such projects do become tainted they would not be easy to fork, operate, or support - which places users and operators at a disadvantage. If a project does inprove their documentation such that self-hosting becomes more accessable, we will of course re-evaluate. Feel free to open a PR.

Contributing Issues

Issues are meant primarily for discussing if something should be added or questions regarding clarification. An issue that says "Add x software" will be treated as a call to community action and labeled with ready-for-pr, provided it meets the above criteria. This is not a problem, but does not necessarily mean the core maintainers of this repo will create that PR for you. However it does mean you or someone else in the community is clear to go ahead and submit a PR for that software. This is maintained in the community's free time, so please understand that there will sometimes be a delay when a PR is created for you.

Please make sure to only submit an Issue for 1 piece of software or section at a time, otherwise it is more difficult to coordinate between multiple Issues and PRs.

We use the following issue types and tags to keep conversation focused and actionable:

• 
• 

Discussion

This is a general issue type and tag to discuss things related to the repo. Before opening this issue type, please read the FAQ.

This is not a place to discuss what you think an "ethical" LLM/AI is. We will close any Issues opened asking for advice on AI/LLM usage.

This is also not a place to open an issue to the effect of "think of the centrists".

If someone has a question in a Discussion type issue, and it requires a hard stance on behalf of the repo, please do not comment with a definitive answer unless you are a maintainer. If you do comment, please explicitly state that you are not an official maintainer, and tag @vleermuis-admin if one has not already responded. There are still situations in which the maintainers will ask for community feedback, and in those, anyone is free to comment. We have these rules to reduce confusion and prevent conflict if there is a mismatch between community members and maintainers. If you feel strongly and want to push back, we are ok with that, but you must do so kindly and in accordance with our Code of Conduct.

More Kind Eyes

Maybe you don't need/want to open an Issue or Pull Request to this repo, but you still want to help. Consider chiming in, kindly, on a Issue. This issue type is for when someone has found, or created, a link to an AI discussion topic. AI discussion topic links can be:

• Bug/Issue in a repo's Issue Tracker
• Discussion on forge sites that support that feature e.g. GitHub Discussions
• PR on an AI Policy where feedback is welcome
• Forum post specifically dedicated to the project and read by the maintainers of the project
• Social media account run by the project and not a solo maintainer. We do not want to call watchers of this repo to approach solo maintainers (there is too much room for that to potentially result in harassment), but if a project/company has a specific social media thread asking for opinions on AI usage in their code base or as a feature of their project/product, feel free to link that.

Anyone can then react (kindly) to a linked upstream issue, pull request, or discussion thread. If you're already a contributor to that project, you may also leave a comment. You must do so kindly though! We do not approve of anyone reaching out in a rude manner to any other projects. If you have no connection to project, the best thing you can do is an emoji react or upvote on the opening discussion topic or to a comment where AI is called out as bad. Please be cautious and courteous. If we find out you were threatening or expressed any form of bigotry, you will receive a ban from this repo.

Important

Reminder that if you post a link to software that is maintained by people who openly embrace bigotry, we will close that issue. If you're a community member and see something we missed, feel free to kindly inform us and we will take action as soon as we're available (typically within 8 hours, but sometimes within 24 hours depending on availability).

If you want to help in that way, search for:

• Issues
• Pull Requests

You can also open your own Issue.

Contributing to the Why Not LLMs section

This is a much more free form section without a specific rigid style guide at this time. Here are some general guidelines:

• Do not link to people's social media posts e.g. fediverse, bsky, X, etc even if they are against AI. Using blog posts is OK, but we'd prefer if the language there was not filled with profanity. We try to keep this repo professional.

• When adding a link to back up your point, please use the name of the source and title of the article as the link name

• Do not use paywalled links unless you are using an archive link that removes the paywall

• Prefer archive links wherever possible

• Use a content warning if anything may be triggering. Content warnings must be specific to the subject matter. Do not use the term "NSFW". Here is an example of how to write a content warning:

<details>
  <summary>Content warning: Genocide</summary>
  Content discussing genocide goes here.
</details>