From 040cc040cb5ab95a010262e3f585ac33185d6217 Mon Sep 17 00:00:00 2001 From: jessebot Date: Fri, 29 May 2026 19:35:46 +0200 Subject: [PATCH] fix removal links --- FAQ.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/FAQ.md b/FAQ.md index 9e419e2..e059f72 100644 --- a/FAQ.md +++ b/FAQ.md @@ -24,11 +24,11 @@ There's no great place to put these in our current files, but these sorts of que ## Why are you targeting/attacking/harassing my favorite project? -> We do not "target", "harass", or "attack" any projects. We, in fact, have a [very strict policy on not doing that](https://codeberg.org/small-hack/open-slopware/src/branch/main/CODE_OF_CONDUCT.md#be-kind-or-be-gone). This repo is one based on ethics and is intended as a call to action. If a project meets the definition of one of our tags, it will see itself added to this repo. It can take steps to stop doing whatever it is in that definition and we'll remove it. (See also the [guide for removal](https://codeberg.org/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md#removal).) +> We do not "target", "harass", or "attack" any projects. We, in fact, have a [very strict policy on not doing that](https://codeberg.org/small-hack/open-slopware/src/branch/main/CODE_OF_CONDUCT.md#be-kind-or-be-gone). This repo is one based on ethics and is intended as a call to action. If a project meets the definition of one of our tags, it will see itself added to this repo. It can take steps to stop doing whatever it is in that definition and we'll remove it. (See also the [guide for removal](https://codeberg.org/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md#removal-of-tainted-status).) ## If a repo had slop before, isn't it permanently tainted? Aren't all forks of slop therefore also slop? -> No. See also: [guide for removal](https://codeberg.org/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md#removal). +> No. See also: [guide for removal](https://codeberg.org/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md#removal-of-tainted-status). > > Eventually, the slop will likely either be removed, replaced, or deprecated. >