open-slopware/CONTRIBUTING.md

## Contributing Pull Requests

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 [Evidence section](#evidence-can-be)). Title the pull request "Add `<software-name>`" or such.

> [!WARNING]
> 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 <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.**

### Criteria

The criteria for being included in this repository are any of:

1. One or more core/prominent developers openly use LLMs *in any level of supportive capacity* to develop this software specifically.
2. The software itself integrates genAI features of any kind, internally or externally.
3. The software actively uses it's README or website real estate to advertise AI.

#### Evidence can be

- social media posts by a core/prominent developer/maintainer advertising AI/LLM usage
- commit history with exact links to the commits
- direct links to an LLM friendly `AGENTS.md` or `CLAUDE.md` (sometimes these are in place to poison LLMs though, so please check the contents first)
- links to pro-AI policy on a software's website or in their repos
- link to release advertising AI usage either to build the software or as a feature of the software
- link to a blog post advertising AI
- section of a README where AI is advertised (even if the software itself doesn't appear to be infected with slop)

Please do not submit GitHub screenshots of "A user you have blocked has previously contributed to this repository". Please instead link directly to the commit hash(s) where this has taken place.

Screenshots are allowed but must be a last resort for something that cannot be linked. We're prefer archive links in all other instances.

### Removal

Any project here may be 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.

## 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 in when a PR is generated 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.

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.

## Helping with kind eyes

Maybe you don't need/want to open an Issue or Pull Request to this repo, but you still want to help. Here's what you can do. Take a look through the:

- **Issues** labeled with [`more-kind-eyes-please`](https://codeberg.org/small-hack/open-slopware/issues?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0) or [`awaiting-upstream-feedback`](https://codeberg.org/small-hack/open-slopware/issues?q=&type=all&state=open&labels=1280479&milestone=0&assignee=0&poster=0)
- **Pull Requests** labeled with [`more-kind-eyes-please`](https://codeberg.org/small-hack/open-slopware/pulls?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0) or [`awaiting-upstream-feedback`](https://codeberg.org/small-hack/open-slopware/pulls?q=&type=all&sort=relevance&labels=1280479&state=open&milestone=0&project=0&assignee=0&poster=0)

In either case, one thing you can do is react positively to a given 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. It's unwise to pop into a discussion for a project you do not use and have no interest in using and only adds noise to the conversation, which could overwhelm the maintainers. 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.
note how issues work This is just so people understand that adding an issue doesn't mean we'll generate a PR for you, only because we are time constrained, but that you're still free to add an Issue and perhaps we or someone else in the community will create a PR for you :) 2026-03-10 11:50:50 +01:00			`## Contributing Pull Requests`
start environment impact section and create CONTRIBUTING.md 2026-01-10 19:22:51 +01:00
Update the CONTRIBUTING docs to address preferred evidence types 2026-03-20 20:58:58 +01:00			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 [Evidence section](#evidence-can-be)). Title the pull request "Add `<software-name>`" or such.
start environment impact section and create CONTRIBUTING.md 2026-01-10 19:22:51 +01:00
Note: advertising AI is still also not ok; allowing a few AI contributions is still not great Also really emphasize how important providing alternatives is 2026-03-09 20:50:23 +01:00			`> [!WARNING]`
			`> 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 <3`

Update the CONTRIBUTING docs to address preferred evidence types 2026-03-20 20:58:58 +01:00			`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.`
Add note to please create individual PRs and Issues to avoid large merge conflicts and confusion 2026-03-17 13:15:48 +01:00
start environment impact section and create CONTRIBUTING.md 2026-01-10 19:22:51 +01:00			`### Criteria`

			`The criteria for being included in this repository are any of:`

Note: advertising AI is still also not ok; allowing a few AI contributions is still not great Also really emphasize how important providing alternatives is 2026-03-09 20:50:23 +01:00			`1. One or more core/prominent developers openly use LLMs in any level of supportive capacity to develop this software specifically.`
start environment impact section and create CONTRIBUTING.md 2026-01-10 19:22:51 +01:00			`2. The software itself integrates genAI features of any kind, internally or externally.`
Update the CONTRIBUTING docs to address preferred evidence types 2026-03-20 20:58:58 +01:00			`3. The software actively uses it's README or website real estate to advertise AI.`

			`#### Evidence can be`

			`- social media posts by a core/prominent developer/maintainer advertising AI/LLM usage`
			`- commit history with exact links to the commits`
note LLM unfriendly vs friendly LLM AGENTS/CLAUDE files 2026-03-20 21:53:15 +01:00			- direct links to an LLM friendly `AGENTS.md` or `CLAUDE.md` (sometimes these are in place to poison LLMs though, so please check the contents first)
Update the CONTRIBUTING docs to address preferred evidence types 2026-03-20 20:58:58 +01:00			`- links to pro-AI policy on a software's website or in their repos`
			`- link to release advertising AI usage either to build the software or as a feature of the software`
			`- link to a blog post advertising AI`
			`- section of a README where AI is advertised (even if the software itself doesn't appear to be infected with slop)`

			`Please do not submit GitHub screenshots of "A user you have blocked has previously contributed to this repository". Please instead link directly to the commit hash(s) where this has taken place.`

			`Screenshots are allowed but must be a last resort for something that cannot be linked. We're prefer archive links in all other instances.`
start environment impact section and create CONTRIBUTING.md 2026-01-10 19:22:51 +01:00
			`### Removal`

Note: advertising AI is still also not ok; allowing a few AI contributions is still not great Also really emphasize how important providing alternatives is 2026-03-09 20:50:23 +01:00			`Any project here may be removed as long as the following become true, even if prior LLM-authored code remains:`
start environment impact section and create CONTRIBUTING.md 2026-01-10 19:22:51 +01:00
			`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.`
note how issues work This is just so people understand that adding an issue doesn't mean we'll generate a PR for you, only because we are time constrained, but that you're still free to add an Issue and perhaps we or someone else in the community will create a PR for you :) 2026-03-10 11:50:50 +01:00
			`## Issues`

Add note to please create individual PRs and Issues to avoid large merge conflicts and confusion 2026-03-17 13:15:48 +01:00			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 in when a PR is generated for you.

reminder that this is not the place for pro-LLM discussion 2026-03-20 18:15:22 +01:00			`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.`

add notes for the contributing docs on how to help 2026-04-12 11:34:28 +02:00			`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.`

			`## Helping with kind eyes`

			`Maybe you don't need/want to open an Issue or Pull Request to this repo, but you still want to help. Here's what you can do. Take a look through the:`

clean up formatting 2026-04-12 11:36:26 +02:00			- Issues labeled with [`more-kind-eyes-please`](https://codeberg.org/small-hack/open-slopware/issues?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0) or [`awaiting-upstream-feedback`](https://codeberg.org/small-hack/open-slopware/issues?q=&type=all&state=open&labels=1280479&milestone=0&assignee=0&poster=0)
			- Pull Requests labeled with [`more-kind-eyes-please`](https://codeberg.org/small-hack/open-slopware/pulls?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0) or [`awaiting-upstream-feedback`](https://codeberg.org/small-hack/open-slopware/pulls?q=&type=all&sort=relevance&labels=1280479&state=open&milestone=0&project=0&assignee=0&poster=0)
add notes for the contributing docs on how to help 2026-04-12 11:34:28 +02:00
			In either case, one thing you can do is react positively to a given 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. It's unwise to pop into a discussion for a project you do not use and have no interest in using and only adds noise to the conversation, which could overwhelm the maintainers. 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.