remote/open-slopware
1
0
Fork 0
mirror of https://codeberg.org/small-hack/open-slopware.git synced 2026-08-30 09:54:03 +02:00
Code Issues Projects Releases Packages Wiki Activity

add deslop section (in HOW_TO_SLOP_FREE_FORK) (#1244)

Browse source 
### Description of Changes

This PR adds a deslop section

Reviewed-on: https://codeberg.org/ethical-foss/open-slopware/pulls/1244
Reviewed-by: Ethical FOSS admin <ethical-foss-admin@noreply.codeberg.org>
This commit is contained in:
Allen123456hello 2026-08-19 18:28:11 +02:00 • committed by Ethical FOSS admin
commit 86f55cfbbd
1 changed files with 18 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

22
HOW_TO_SLOP_FREE_FORK.md
View file

@ -162,10 +162,7 @@ Let's take tldr-pages as an example, as that was something the community recentl
got send -f
```
8. The initial steps are now done and your new forked repo's history starts at the exact last known good version. Advanced git users can now cherry pick LLM commits out of the repo, but we recommend not doing that unless you're very confident with git. Instead, we think it's best that you create new commits to remove the AI and LLM generated code, because then this also keeps a cleaner history. In your "No AI Policy" or in your README, you can self disclose that the repo contains old commits from an LLM, but that you're working on replacing them or that you will not replace old commits, but all new commits will be done by humans. Either is fine. When it comes to AI Functionality, you'll also want to disclose that immediately and perhaps create an issue that says "Remove AI Functionality" to show users that you intend to remove that. You could also ask for help that that time.
> [!note]
> Are you an advanced git user? Do you want to add more docs here on how to remove old LLM commits from the forked repo? Feel free to submit a PR and we'll test your instructions to make sure they're safe before merging it :)
8. The initial steps are now done and your new forked repo's history starts at the exact last known good version. Advanced git users can now cherry pick LLM commits out of the repo, but we recommend not doing that unless you're very confident with git. Instead, we think it's best that you create new commits to remove the AI and LLM generated code ("Deslopping"), because then this also keeps a cleaner history. In your "No AI Policy" or in your README, you can self disclose that the repo contains old commits from an LLM, but that you're working on replacing them or that you will not replace old commits, but all new commits will be done by humans. Either is fine. When it comes to AI Functionality, you'll also want to disclose that immediately and perhaps create an issue that says "Remove AI Functionality" to show users that you intend to remove that. You could also ask for help that that time.
## Tips for a healthy community
@ -260,6 +257,23 @@ But in general you want to outline the following:
Do your best to not leave any wiggle room for anyone testing the waters on using AI in any way, this includes "self hosted LLMs".
### Deslopping
After making a slop-free fork, you can try to remove slops from the fork.
Here's how a deslop script was made:
1. Search for slop commits and slop files. You can use some scripts to do some automatic searching.
2. Re-check the project by hand. Make sure you have found all the slops.
3. Write a script revert slop commits and remove slop files.
Here is an example: [i3-deslop](https://codeberg.org/Allen123456hello/i3-deslop)
> [!note]
> If you have your own "deslopping" script, feel free to submit a PR to add it as an example.
## Advertising your new fork
We're so happy to hear you created a new slop free fork! You'll probably want some community help though. Here's what you can do to summon the open source community: