mirror of
https://codeberg.org/small-hack/open-slopware.git
synced 2026-05-28 12:56:22 +02:00
Compare commits
1 commit
| Author | SHA1 | Date | |
|---|---|---|---|
|
5799ceeaac |
15 changed files with 446 additions and 2013 deletions
|
|
@ -1,55 +0,0 @@
|
|||
name: Call for Collaborators for a New AI-free Project
|
||||
about: Put out a call for collaborators on a new or recently forked project that has an explicit No AI policy. (must have a code of conduct)
|
||||
title: "[Call for Collaborators]: project name here"
|
||||
ref: "main"
|
||||
labels:
|
||||
- call-for-collaborators
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
Thanks for helping to make the world a bit more AI free 💙
|
||||
The idea here is to request help with forking or rewriting a currently tainted project.
|
||||
|
||||
- type: input
|
||||
id: project
|
||||
attributes:
|
||||
label: What's the name of the project?
|
||||
description: |
|
||||
What is the name or idea behind the project you want to start/have started?
|
||||
|
||||
- type: input
|
||||
id: link
|
||||
attributes:
|
||||
label: Link
|
||||
description: |
|
||||
Provide a link to the new repo you've created (this can be a fork or a fresh rewrite).
|
||||
|
||||
- type: input
|
||||
id: language
|
||||
attributes:
|
||||
label: Programming Language
|
||||
description: |
|
||||
What programming language will this be primarily written in?
|
||||
|
||||
- type: textarea
|
||||
id: additional-info
|
||||
attributes:
|
||||
label: Additional Info
|
||||
description: |
|
||||
Tell us what the project is about. Is it a fork? Is it a fresh rewrite? Which project on the tainted list would it be an alternative to? What do you intend to do with it? Do you need maintainers? Collaborators? Reviewers? Contributors? Documentation writers? How can we help? :)
|
||||
|
||||
- type: checkboxes
|
||||
id: terms
|
||||
attributes:
|
||||
label: Code of Conduct and Rules for Collaboration
|
||||
description: By submitting this issue, you agree to follow our [Code of Conduct](https://codeberg.org/small-hack/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
|
||||
options:
|
||||
- label: I agree to follow this project's Code of Conduct
|
||||
required: true
|
||||
- label: The project I want to collaborate on has a No AI policy banning any and all AI usage
|
||||
required: true
|
||||
- label: The project I want to collaborate on is free and open source.
|
||||
required: true
|
||||
- label: The project I want to collaborate on has an explicit code of conduct banning bigotry.
|
||||
required: true
|
||||
|
|
@ -2,9 +2,6 @@
|
|||
blank_issues_enabled: false
|
||||
|
||||
contact_links:
|
||||
- name: Our Contributing Doc
|
||||
url: https://codeberg.org/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md
|
||||
about: Read this to learn how you can contribute to this project ✨
|
||||
- name: How to Create a Pull Request
|
||||
url: https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/
|
||||
about: Learn more about how to create a pull request on codeberg 🩵
|
||||
- name: Small Hack
|
||||
url: https://codeberg.org/small-hack
|
||||
about: Visit our org's homepage
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
name: Discussion
|
||||
about: Open a discussion topic for the community. Please don't use this to say "add software". Open a Pull Request if you want to do that.
|
||||
about: Open a discussion topic for the community
|
||||
title: '[Discussion]: '
|
||||
ref: 'main'
|
||||
labels:
|
||||
|
|
@ -15,8 +15,8 @@ body:
|
|||
label: Discussion Topic
|
||||
description: |
|
||||
Please let us know what you'd like to discuss.
|
||||
Remember that if you already have concrete evidence, you should just open a PR. Pleae don't create an Issue.
|
||||
This is also not a place to ask advice on using your own LLMs.
|
||||
Remember that if you already have concrete evidence, you can just open a PR. You don't need to create an Issue.
|
||||
This is not a place to ask advice on using your own LLMs.
|
||||
- type: checkboxes
|
||||
id: terms
|
||||
attributes:
|
||||
|
|
|
|||
|
|
@ -3,12 +3,10 @@
|
|||
- 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 albeism.
|
||||
- No classism.
|
||||
- No fascism.
|
||||
|
||||
|
|
@ -32,11 +30,11 @@ That will display like this:
|
|||
homophobic content goes here.
|
||||
</details>
|
||||
|
||||
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.
|
||||
Failure to do so will first result in a one time warning and future offenses will be considered a strike.
|
||||
|
||||
# On handling rude comments in this repo specifically
|
||||
|
||||
If you see someone behaving in appropriately, do not feed their behavior. Tag @vleermuis-admin instead. They will handle it.
|
||||
If you see someone behaving in appropriately, do not feed their behavior. Tag an admin (@jessebot or @cloudymax) instead. They will handle it.
|
||||
|
||||
## Strike system
|
||||
|
||||
|
|
@ -53,10 +51,6 @@ We're going to do a 2 strike rule here with an optional warning. You are out on
|
|||
|
||||
# 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](https://codeberg.org/small-hack/open-slopware/src/branch/main/NO_AI_REQUEST_TEMPLATE.md#tips-for-success). You are also free to copy and paste anything from the [Why not LLMs](https://codeberg.org/small-hack/open-slopware/src/branch/main#why-not-llms) section of our README.
|
||||
|
||||
- We don't want drive by sarcastic comments.
|
||||
|
||||
- No references to bodily fluids (vomit, urine, feces), this includes emojis. It's gross and unproductive.
|
||||
|
|
@ -69,26 +63,10 @@ We're going to do a 2 strike rule here with an optional warning. You are out on
|
|||
|
||||
- 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.
|
||||
- Do **NOT** use this repo as a witch hunting device in any direction. You may not reach out on social media, reddit, messaging apps, etc, especially not in a rude way, to maintainers of other repos to harass them and threaten them with this list. Doing so will result in a ban.
|
||||
|
||||
- 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.
|
||||
|
||||
## Gender Neutral Language
|
||||
|
||||
When referring 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:
|
||||
|
||||
- [What are personal pronouns and why do they matter?](https://pronouns.org/what-and-why)
|
||||
- [Gender-Neutral Pronouns 101: Everything You've Always Wanted to Know](https://www.them.us/story/gender-neutral-pronouns-101-they-them-xe-xem)
|
||||
- [Dictionary of gender neutral language](https://en.pronouns.page/dictionary)
|
||||
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 reddit type atmosphere here and won't tolerate it. Please consider your words before you hit send.
|
||||
|
||||
## 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.
|
||||
Please provide alt text description 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 just 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 just ask others to provide alt text for you for ANY reason.)
|
||||
|
|
@ -1,6 +1,3 @@
|
|||
> [!warning]
|
||||
> Before you interact with this repo, please read the [**Code of Conduct**](./CODE_OF_CONDUCT.md)! This is a repo for *nice people only*!
|
||||
|
||||
# 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 [Criteria](#criteria)).
|
||||
|
|
@ -27,9 +24,6 @@ Other tips for keeping the repo tidy and making sure we don't duplicate efforts:
|
|||
```
|
||||
- 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).
|
||||
|
||||
> [!note]
|
||||
> Don't know how to create a PR? You can learn more about that in the [Codeberg Pull Requests and Git Flow docs](https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/) 🩵
|
||||
|
||||
## 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:
|
||||
|
|
@ -41,12 +35,9 @@ The criteria for being included in this repository are any of following tags. Yo
|
|||
- [](https://codeberg.org/small-hack/open-slopware#gen-ai-art)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#ai-databroker-usage)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#ai-in-issue-tracker)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#permits-llm-ingestion)
|
||||
|
||||
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](./STYLE.md) to ensure you are conforming to our community agreed upon standards.
|
||||
|
|
@ -59,9 +50,7 @@ Any project here may be removed as long as the following become true, *even if p
|
|||
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.
|
||||
|
||||
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 [](https://codeberg.org/small-hack/open-slopware#ai-code-reviews), but keeps a [](https://codeberg.org/small-hack/open-slopware#permissive-ai-policy). 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](./NO_AI_REQUEST_TEMPLATE.md) for inspiration 🙏
|
||||
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 AI code reviews, but keeps a permissive AI policy. Updates are always welcome.
|
||||
|
||||
# Issues
|
||||
|
||||
|
|
@ -84,4 +73,4 @@ In either case, one thing you can do is react positively to a given upstream iss
|
|||
|
||||
# Social media
|
||||
|
||||
We would 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. Please also don't quote social media posts in the "Why not LLMs" section.
|
||||
We would 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.
|
||||
|
|
|
|||
71
FAQ.md
71
FAQ.md
|
|
@ -1,71 +0,0 @@
|
|||
# Frequently Asked Questions
|
||||
|
||||
There's no great place to put these in our current files, but these sorts of questions come up enough, that we wanted to put them down somewhere to easily link responses.
|
||||
|
||||
## Can I self-advertise my project (that doesn't use AI)?
|
||||
|
||||
> Yes, provided it's FOSS, has a code of conduct (even if it's a solo project), and a No AI Policy, you can add your project as an alternative to any tainted software in which it is a good fit, and you can also open a [Call for Collaborators Issue](https://codeberg.org/small-hack/open-slopware/issues/new?template=.forgejo%2fissue_template%2fcollaborate-with-me.yaml).
|
||||
|
||||
## I use AI in my project and do not plan on stopping. Should I self-submit?
|
||||
|
||||
> You don't have to, but it's helpful, because you know best what the alternatives are, and when your last untainted commit was, which is helpful for those who wish to fork your project. We hope you'll consider dropping AI one day, for all the reasons we've listed in our [Why Not LLMs?](https://codeberg.org/small-hack/open-slopware#why-not-llms) section, but if you don't plan on doing that ever, please just be cordial in this repo. No one is here to attack you, and if they do, please tag @vleermuis-admin and we'll handle the situation.
|
||||
|
||||
## Do closed source or proprietary products belong on this list?
|
||||
|
||||
> No, this repo is only for open source projects.
|
||||
|
||||
## Can we split the "Permissive AI Policy" tag further?
|
||||
|
||||
> No, beyond "vibecoded" being added in some extreme cases. We don't want to have this conversation continually, as it is subjective what "severity" something falls under. The decision to add these tags took us a long time, and unless you have another *specific* tag that cannot be covered under any other tag, we're currently not open to discussion about this. This repo is already quite a lot to manage.
|
||||
|
||||
## What if the AI code is human reviewed?
|
||||
|
||||
> Slop that is human reviewed is still slop. We are against AI for more than just code quality reasons. Please see our [Why Not LLMs?](https://codeberg.org/small-hack/open-slopware#why-not-llms) section.
|
||||
|
||||
## 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).)
|
||||
|
||||
## 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).
|
||||
>
|
||||
> Eventually, the slop will likely either be removed, replaced, or deprecated.
|
||||
>
|
||||
> We're also against AI for more than just code quality reasons. There's plenty of ethical reasons to be against continuing to use AI:
|
||||
>
|
||||
> - [environmental](https://codeberg.org/small-hack/open-slopware#environmental-impact)
|
||||
> - [ties to the war industrial complex](https://codeberg.org/small-hack/open-slopware#ties-to-the-war-industrial-complex)
|
||||
> - [effect on hardware prices hurting newcomers to the industry](https://codeberg.org/small-hack/open-slopware#effect-on-hardware-prices) (especially those already disenfranchised)
|
||||
>
|
||||
> The commitment to stop using AI stops those above ethical issues. It's like going vegetarian. You're still a vegetarian if you previously consumed meat, but now you don't. You've still reduced suffering and helped the environment. A commitment to doing better is better than never stopping a harmful action.
|
||||
|
||||
## Is a project tainted if it has dependencies that are tainted?
|
||||
|
||||
> This one is complicated, but in short: No, unless the dependencies are literally AI libraries.
|
||||
> If the dependency is, for example, the ChatGPT SDK or something similar, then yes, the project is tainted.
|
||||
> If the project is just built with something like Python, which is also tainted, we do not automatically consider it tainted, as the language is a general purpose language and there are *very* few languages not already tainted or slated to be tainted right now. We take a harm reduction philosophy and we believe that, especially in the case of established projects, demanding that they switch the core language of their project is not a simple undertaking.
|
||||
|
||||
## Can you advise us on the ethical usage of AI?
|
||||
|
||||
> No, but you may find the work of [DAIR](https://dair-institute.org/) interesting. Also, see our [Why not LLMs?](https://codeberg.org/small-hack/open-slopware#why-not-llms) section.
|
||||
|
||||
## What about "Open Source AI"?
|
||||
|
||||
> Yes, simply being open source does not resolve the issues listed in our [Why Not LLMs?](https://codeberg.org/small-hack/open-slopware#why-not-llms) section and thus such projects will still be included on this list.
|
||||
|
||||
## Why is removal harder than landing on the list in the first place?
|
||||
|
||||
> Because the project betrayed our trust. Now they have to try harder to rebuild that by committing to doing better in an accountable, public, concreate, and enforceable way. If the project is committed to doing better by rejecting AI in the future, putting out a No AI policy or updating their contributing docs, shouldn't be that difficult.
|
||||
|
||||
## Why can't I include an social media post?
|
||||
|
||||
> We do not want to have a social media type atmosphere here and quoting social media posts, no matter what side people are on, gets messy. The mtaintiners here do not have the mental health to engage in social media drama that inevitably arises from AI bros, nor do we want to inflict that on anyone who is unaware of this list and hasn't consented to that attention. This does not mean you should reach out to your favorite anti-AI influencer for permission to include them in this list. We don't want you to do that.
|
||||
|
||||
### But what if it's a social media post against AI?
|
||||
|
||||
> We would then need to research those social media users and see if we endorse them or not and we don't want to do that either.
|
||||
|
||||
## I don't like your definition of slop or vibecoded. Can you change it?
|
||||
|
||||
> No. Those [definitions](https://codeberg.org/small-hack/open-slopware#definitions) stay and are not up for debate.
|
||||
|
|
@ -1,217 +0,0 @@
|
|||
# How to create a slop free fork
|
||||
|
||||
So you found out something you love is tainted with slop and now you want to do something about it?
|
||||
|
||||
First off, congrats and thank you! That's a huge step and we're excited for the community you build! 💙
|
||||
|
||||
## How to fork a repo from a last untainted commit/version
|
||||
|
||||
Should you see a project you'd really like to fork on this list, here's how you would go about that.
|
||||
|
||||
> [!warning]
|
||||
> Before you fork, make sure to check the licensing! It's important that you understand the license of whatever you fork, and never remove the old LICENSE. Safe to fork licenses include, but are not limited to: MIT, GPL, AGPL, Apache 2.0, CCv4, BSD. You can learn more about licensing in [Codeberg's documentation on licensing](https://docs.codeberg.org/getting-started/licensing/).
|
||||
|
||||
Let's take tldr-pages as an example, as that was something the community recently hard forked into ethical-tldr. Here's how it was done.
|
||||
|
||||
1. Setup a new home for your fork. We recommend using [codeberg.org](https://codeberg.org)! Codeberg has [great docs on setting up your first repo](https://docs.codeberg.org/getting-started/first-repository/). We recommend not adding a `.gitignore`, `LICENSE`, or `README` to start with, because your clone will likely already have those and so you want to make sure you don't run into any git merge conflicts :) Do make sure to note that your repo is a fork of the repo you're forking at first though, just to make sure no one gets confused.
|
||||
|
||||
2. Since we're using tldr as an example, we'll assume the project you want to fork is already in this repo. Go to the table where the software you want to fork is (for instance the [Cheat Sheets and Documentation section](https://codeberg.org/small-hack/open-slopware#cheat-sheets-and-documentation)), which looked like this:
|
||||
|
||||
| Name | Last Untainted Version or Commit ID | Tags and Evidence | Alternative(s) |
|
||||
| --- |:---:| --- | --- |
|
||||
| [tldr-pages](https://github.com/tldr-pages/tldr) | [`v2.3`](https://github.com/tldr-pages/tldr/releases/tag/v2.3) | [](#permissive-ai-policy) ([1](https://github.com/tldr-pages/tldr/blob/main/AGENTS.md), [2](https://github.com/tldr-pages/tldr/commit/b042736266e10cb026b678ba1d0fed362d5f579d)) | [](#request-for-help) |
|
||||
|
||||
3. Go to the source repo and find the clone URL. In this case, you would go to [tldr-pages](https://github.com/tldr-pages/tldr). Since it's on GitHub, you should see a green button that says "<> Code". Click the green button, then click "HTTPS" and you should be able to copy that URL.
|
||||
|
||||
<img src="./img/how_to/clone_tldr.png" alt="a screenshot of the https://github.com/tldr-pages/tldr page where someone has clicked the code button. The green code button is circled in orange with an orange arrow pointing to it. The HTTPS tab and the web URL to clone also have an orange square around them with an orange arrow pointing to the url">
|
||||
|
||||
> [!tip]
|
||||
> In the above case, the tldr repo was linked in the first column of the table, but in cases where it's not you can just click the lasted untainted version link and chop off everything after the name of the project, so https://github.com/tldr-pages/tldr/releases/tag/v2.3 becomes https://github.com/tldr-pages/tldr
|
||||
|
||||
4. Open up a terminal and find a directory where you'd like to keep this project. Then clone the repo there. Here is an example where we keep things in the projects directory within your home directory:
|
||||
|
||||
```bash
|
||||
# creates a directory called projects in your ~, which is your home directory
|
||||
mkdir -p ~/Projects
|
||||
|
||||
# change your current directory into the new projects directory
|
||||
cd ~/Projects
|
||||
|
||||
# clones the repo in your projects directory
|
||||
git clone https://github.com/tldr-pages/tldr.git
|
||||
|
||||
# changes directory to your recently cloned project (in this example, it's the tldr repo)
|
||||
cd tldr
|
||||
```
|
||||
|
||||
5. Grab the new location of your new repo :) If you're using codeberg, you want to grab the SSH url for cloning, which you can find just below the repo stats. We've highlighted it and also we show you the button you can click to copy it easily here:
|
||||
|
||||
<img src="./img/how_to/copy_new_repo_url_codeberg.png" alt="Screenshot of the top of the page for https://codeberg.org/small-hack/ethical-tldr where we've highlighted the clone url and drawn orange arrows pointing to the word SSH, the URL, and the copy button. They exist just below the repo states, but before the repo's code search bar and repo files">
|
||||
|
||||
6. Change the upstream origin of your repo to be your new fork's SSH URL. There are two ways to do this. The first way is to use the `git` command:
|
||||
|
||||
```bash
|
||||
git remote set-url origin ssh://git@codeberg.org/small-hack/ethical-tldr.git
|
||||
```
|
||||
|
||||
Another way is to edit the `.git/config` file Use your editor of choice to open the following file:
|
||||
|
||||
```bash
|
||||
# We're using neovim here, but you can use any editor you're comfortable with.
|
||||
# If you're new, nano is always a safe bet as it has tips at the bottom of the screen.
|
||||
neovim .git/config
|
||||
```
|
||||
|
||||
The file will look like this:
|
||||
|
||||
```config
|
||||
[core]
|
||||
repositoryformatversion = 0
|
||||
filemode = true
|
||||
bare = false
|
||||
logallrefupdates = true
|
||||
[remote "origin"]
|
||||
url = https://github.com/tldr-pages/tldr.git
|
||||
fetch = +refs/heads/*:refs/remotes/origin/*
|
||||
[branch "main"]
|
||||
remote = origin
|
||||
merge = refs/heads/main
|
||||
```
|
||||
|
||||
You want to change your the value of "url" to your new SSH URL. In this case, it would look like this, since the new repo is ethical-tldr:
|
||||
|
||||
```config
|
||||
[core]
|
||||
repositoryformatversion = 0
|
||||
filemode = true
|
||||
bare = false
|
||||
logallrefupdates = true
|
||||
[remote "origin"]
|
||||
url = ssh://git@codeberg.org/small-hack/ethical-tldr.git
|
||||
fetch = +refs/heads/*:refs/remotes/origin/*
|
||||
[branch "main"]
|
||||
remote = origin
|
||||
merge = refs/heads/main
|
||||
```
|
||||
|
||||
7. Here comes the part where you check out the last known untainted commit or version. In this case, the last version of `v2.3`. You can do a hard reset of your fork to that exact version. This drops all the commits after that. To do that, run the following:
|
||||
|
||||
```bash
|
||||
# hard reset your branch to the old commit or version
|
||||
git reset --hard v2.3
|
||||
|
||||
# force push up your now untainted repo
|
||||
git push --force
|
||||
```
|
||||
|
||||
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 :)
|
||||
|
||||
## Tips for a healthy community
|
||||
|
||||
To start off, we recommend you do two things:
|
||||
|
||||
- Create a "Code of Conduct"
|
||||
- Create a "No AI Policy"
|
||||
|
||||
### Code of Conduct
|
||||
|
||||
This may seem like it's not related to the whole "No AI" thing we're all about, but it's incredibly important to creating safe and healthy communities. There will be people who try to cross lines and it's important that from outset, you both create rules for what is not allowed, and a process for enforcing those rules. We recommend the following be added to a `CODE_OF_CONDUCT.md` at the root level of your repo, immediately (this is straight from our own code of conduct):
|
||||
|
||||
<details>
|
||||
|
||||
<summary><code>CODE_OF_CONDUCT.md</code> example</summary>
|
||||
|
||||
```md
|
||||
# Code of Conduct
|
||||
|
||||
## No Bigotry
|
||||
|
||||
- No racism.
|
||||
- No xenophobia.
|
||||
- No colorism/featurism.
|
||||
- No casteism.
|
||||
- No transphobia.
|
||||
- No homophobia/queerphobia.
|
||||
- No sexism.
|
||||
- No albeism.
|
||||
- No islamophobia, antisemitism, or hatred to anyone based on their religion or lack thereof.
|
||||
- No classism.
|
||||
- No fascism.
|
||||
|
||||
## Strike system
|
||||
|
||||
We're going to do a 2 strike rule here with an optional warning. You are out on your second strike. We are not doing three strikes.
|
||||
|
||||
1. **warning**: 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](#no-bigotry) rules, or if you are clearly operating in bad faith.
|
||||
|
||||
2. **Strike one**: You made a comment that was off-base, slightly rude, but was not egregious enough to be banned, yet.
|
||||
|
||||
3. **Strike two**: After 1 strike, you behaved the same way again.
|
||||
|
||||
> [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.
|
||||
|
||||
# Be kind or be gone
|
||||
|
||||
- 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.
|
||||
|
||||
## 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.)
|
||||
```
|
||||
|
||||
</details>
|
||||
|
||||
If you do not outline exactly what is and is not allowed, you will get a lot of people saying "I didn't know I couldn't do that" and it will make enforcing your boundaries difficult. People will always disagree with some decisions you and your community make, and they will want to "take it offline", so it's important that you do not allow that, or your personal social media and messaging will become bad for your mental health. If you'd like to set up a social media account/server or a chat server, we recommend keeping it separate from your personal accounts, so that you have an easy way to disconnect at the end of the day or on your weekends.
|
||||
|
||||
### No AI Policy
|
||||
|
||||
This one is obvious in this repo, but in other repos, it's always important to set clear expectations. Failure to do so may cause people to test the boundaries and also land you on this list. We don't say that to be threatening, but our community takes a complete hard line stance on ALL AI/LLM usage.
|
||||
|
||||
Some examples of "No AI Polices" that you can take take a look at for inspiration are:
|
||||
|
||||
- [wafrn's Contributring Doc](https://codeberg.org/wafrn/wafrn/src/branch/main/CONTRIBUTING.md)
|
||||
|
||||
- [Loupe's Use of Generative AI Policy](https://discourse.gnome.org/t/loupe-no-longer-allows-generative-ai-contributions/27327)
|
||||
|
||||
But in general you want to outline the following:
|
||||
|
||||
- No AI or LLM usage is allowed in this repo for contributions in Issues, Pull Requests, or Discussions. This includes bug finding, optimizations, security passes.
|
||||
- You are not permitted to ingest this repo with AI or LLMs of any kind
|
||||
- Any AI generated PRs will be rejected.
|
||||
- We do not accept funding from AI companies.
|
||||
|
||||
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".
|
||||
|
||||
## 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:
|
||||
|
||||
1. Make sure your repo has all the appropriate and relevant topics, so for example, if you've forked the tldr-pages repo, tag the repo with `tldr`, and `cheatsheets`. Topics are managed the main page of your repository, directly under your repo's description.
|
||||
|
||||
|
||||
### Adding new collaborators
|
||||
|
||||
Codeberg also has great docs on [how to add new collaborators](https://docs.codeberg.org/collaborating/invite-collaborators/)!
|
||||
|
||||
> [!warning]
|
||||
> Ensure you trust anyone you give access to your repo. Don't add people as collaborators whom you've never interacted with before!
|
||||
|
|
@ -1,196 +0,0 @@
|
|||
# Reaching Out to a Project
|
||||
|
||||
Below you'll find a couple of basic templates you can use to reach out to a project in order to politely ask them to consider creating a No AI Policy. We're creating a couple of different templates depending on which angle you think might be most appealing to a given a project. You're also free to combine sections of different templates together to hit many different points in a single post. This is meant to be a starting point, not the final iteration.
|
||||
|
||||
Before you proceed, read our [Tips for Success](#tips-for-success).
|
||||
|
||||
Would you like to improve these templates or add additional sections? Please feel free to submit a PR to do so and we'll discuss it :)
|
||||
|
||||
## Tips for Success
|
||||
|
||||
- Do this in the public forum, issue tracker, discussions, etc.
|
||||
- Avoid using direct messages (otherwise you'd need to share screenshots of your direct message which could cause friction)
|
||||
- Avoid using places like discord servers unless that is the ONLY place a project does Issue Triage
|
||||
- Personalize the template a bit before sending it:
|
||||
- Add how long you've been using the software.
|
||||
- Add what the project means to you.
|
||||
- Add the name of the project in the opening
|
||||
- Add your name at the bottom.
|
||||
- Be nice! *We cannot stress this enough*: Be Kind!
|
||||
- Do not shame or threaten the project you are reaching out to, especially not with this list.
|
||||
- You may not want to include every section, depending on the culture surrounding the project you are contacting. Use your best judgement.
|
||||
|
||||
# Templates
|
||||
|
||||
* [Appeal to Ethics Template](#appeal-to-ethics-template)
|
||||
* [Appeal to Code Quality Template](#appeal-to-code-quality-template)
|
||||
* [Appeal to Fear of Legal Ramfification Template](#appeal-to-fear-of-legal-ramfification-template)
|
||||
|
||||
## Appeal to Ethics Template
|
||||
|
||||
```markdown
|
||||
Hello,
|
||||
|
||||
I'd like to talk about your AI policy. Below are some reasons why using AI can be harmful:
|
||||
|
||||
## Environmental Impact
|
||||
|
||||
To start learning a bit more, you can check out the Wikipedia page on the [environmental impact of artificial intelligence](https://en.wikipedia.org/wiki/Environmental_impact_of_artificial_intelligence#Individual_level). Here's some more specific sources:
|
||||
|
||||
- [MIT News: Generative AI's environmental impact](https://news.mit.edu/2025/explained-generative-ai-environmental-impact-0117)
|
||||
|
||||
- [MIT Technology Review: We did the math on AI's energy footprint. Here's the story you haven't heard.](https://www.technologyreview.com/2025/05/20/1116327/ai-energy-usage-climate-footprint-big-tech/)
|
||||
|
||||
## Effect on Hardware Prices
|
||||
|
||||
The demand for construction and outfitting of new data-centers to host AI/LLM compute capacity has overwhelmed global supply and production of multiple hardware components. Memory, Storage, and GPUs have seen massive increases in price for both consumer and enterprise models, upwards of 400% in some cases.
|
||||
|
||||
The lack of supply has led large system-builders to purchase production capacity from OEMs well in advance of delivery, leading some manufacturers to end consumer-oriented product lines in favor of enterprise capacity.
|
||||
|
||||
The downstream effects for consumers is that nearly all electronic devices which contain memory and storage will see their prices rise and availability decline. Those who already own existing electronics and computer hardware components may also find themselves unable to have their devices repaired or replaced under warranty.
|
||||
|
||||
- [The RAM shortage is coming for everything you care about](https://www.theverge.com/tech/880812/ramageddon-ram-shortage-memory-crisis-price-2026-phones-laptops)
|
||||
|
||||
- [Western Digital is already sold out of hard drives for all of 2026 — chief says some long-term agreements for 2027 and 2028 already in place](https://www.tomshardware.com/pc-components/hdds/western-digital-is-already-sold-out-of-hard-drives-for-all-of-2026-chief-says-some-long-term-agreements-for-2027-and-2028-already-in-place)
|
||||
|
||||
- [The 2026 storage crisis: Why AI data centers are hoarding every hard drive on the market](https://www.howtogeek.com/dont-count-on-hdds-to-save-you-from-rising-storage-costs/)
|
||||
|
||||
This has resulted in pricing historically marginalized individuals, who are more likely to have less financial resources, out of learning about computers at home and shrinking the diversity of the computing and programming industry.
|
||||
|
||||
## Ties to the War Industry
|
||||
|
||||
A lot of AI companies also work directly with nation states for use in their War Departments, which in turn leads to further AI usage during war and invasions. This is coupled with [NYT: Palantir, Anthropic and small start-ups are generating rewards from their investments in defense tech](https://www.nytimes.com/2026/03/18/technology/silicon-valley-war-defense-tech.html).
|
||||
|
||||
As another example [NPR: OpenAI announced Pentagon deal after Trump banned Anthropic](https://www.npr.org/2026/02/27/nx-s1-5729118/trump-anthropic-pentagon-openai-ai-weapons-ban) which was due to the USA Department of War [launching an AI acceleration strategy](https://web.archive.org/web/20260113071131/https://www.war.gov/News/Releases/Release/Article/4376420/war-department-launches-ai-acceleration-strategy-to-secure-american-military-ai/).
|
||||
|
||||
Due to the nature of LLMs being only kind of as good as the data they are trained on, this can lead to additional civilian deaths and housing/infrastructure damage either intentionally or not. Examples:
|
||||
|
||||
<details>
|
||||
<summary>Content Warning: War details, death</summary>
|
||||
|
||||
- [Gaza: UN experts deplore use of purported AI to commit ‘domicide’ in Gaza, call for reparative approach to rebuilding](https://www.ohchr.org/en/press-releases/2024/04/gaza-un-experts-deplore-use-purported-ai-commit-domicide-gaza-call)
|
||||
- [Lavender & Where’s Daddy: How Israel Used AI to Form Kill Lists & Bomb Palestinians in Their Homes](https://www.democracynow.org/2024/4/5/israel_ai)
|
||||
- [Microsoft says it provided AI to Israeli military for war](https://apnews.com/article/microsoft-israel-military-gaza-hamas-artificial-intelligence-20b2adb438b39ee9cb6eb2f52c1ae44a)
|
||||
- [Google has dropped its promise not to use AI for weapons](https://theconversation.com/google-has-dropped-its-promise-not-to-use-ai-for-weapons-its-part-of-a-troubling-trend-249169)
|
||||
- ["We want to use it for everything": How Project Maven became central to America’s AI-powered warfare](https://web.archive.org/web/20260312035736/https://www.independent.co.uk/news/world/americas/project-maven-ai-us-airstrike-iraq-anthropic-b2929138.html)
|
||||
|
||||
</details>
|
||||
|
||||
## What You Can Do
|
||||
|
||||
I'd like to kindly suggest implementing a strict "No AI" policy. This can also help with what seems to be larger and larger influxes of low quality drive-by PRs by AI agents.
|
||||
|
||||
You can find other projects that have taken steps to say no to AI here:
|
||||
https://noai.starlightnet.work/list.html
|
||||
|
||||
For a specific policy, I can recommend the following policies for inspiration:
|
||||
|
||||
- [wafrn's Contributring Doc](https://codeberg.org/wafrn/wafrn/src/branch/main/CONTRIBUTING.md)
|
||||
|
||||
- [Loupe's Use of Generative AI Policy](https://discourse.gnome.org/t/loupe-no-longer-allows-generative-ai-contributions/27327)
|
||||
|
||||
Thank you and kind regards :pray:
|
||||
```
|
||||
|
||||
## Appeal to Code Quality Template
|
||||
|
||||
```markdown
|
||||
Hello,
|
||||
|
||||
I'd like to talk about your AI policy. Below are some reasons why using AI can result in poorer code quality:
|
||||
|
||||
## Poor Code Quality
|
||||
|
||||
Vibe coding / agentic workflows result in poorer code quality, and relaxed oversight practices. These effects may be compounded by the common practice of using additional LLM-based tooling to provide code-reviews.
|
||||
|
||||
* [How I Dropped Our Production Database and Now Pay 10% More for AWS](http://archive.today/2026.03.06-144058/https://alexeyondata.substack.com/p/how-i-dropped-our-production-database)
|
||||
* [Claude Tested Everything Except the One Thing That Mattered (AI agent refuses to follow explicit instructions to test `createPost()` in increasingly erratic ways)](http://archive.today/2026.03.09-201135/https://christophermeiklejohn.com/ai/claude/2026/03/08/claude-tested-everything-except-the-one-thing-that-mattered.html)
|
||||
* [Amazon calls engineers for a “deep dive” internal meeting to discuss “GenAI”-related outages](https://ghostarchive.org/archive/3TfgF)
|
||||
* GitClear has released reports in [2024](https://www.gitclear.com/coding_on_copilot_data_shows_ais_downward_pressure_on_code_quality) and [2025](https://www.gitclear.com/ai_assistant_code_quality_2025_research) indicating a worsening of key code quality metrics correlating with increased LLM adoption.
|
||||
|
||||
### Deskilling
|
||||
|
||||
There is increasing evidence to show that LLMs negatively impact developers' coding abilities:
|
||||
|
||||
* [Brains show less activity when completing tasks with LLMs](https://arxiv.org/abs/2506.08872) compared to completing tasks with search or completing tasks without digital help.
|
||||
* [Developers who use early-2025 LLMs](https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/) reported higher subjective performance, but were measured to have lower objective performance. This gap between subjective and objective performance was considered notable.
|
||||
* In an [Anthropic study](https://www.anthropic.com/research/AI-assistance-coding-skills), learners using LLMs demonstrated lower learning rates on average compared to learners not using LLMs.
|
||||
* [A recent study uses the term "cognitive surrender"](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6097646) to describe the way humans tend to offload key critical thinking skills onto LLMs, even when the output is wrong.
|
||||
* A paper entitled ["AI Assistance Reduces Persistence and Hurts Independent Performance"](https://arxiv.org/abs/2604.04721) from April 2026 by academics from MIT, Oxford, UCLA, and Carnegie Mellon showed alarming evidence that performing a variety of tasks with the help of AI for only 10 minutes causes "inpaired unassisted performance and reduced persistence". The researchers noted that "although AI assistance improves performance in the short-term, people perform significantly worse without AI and are more likely to give up"; they also pointed out that "these findings are particularly concerning because persistence is foundational to skill acquisition and is one of the strongest predictors of long-term learning".
|
||||
|
||||
### Infosec risks
|
||||
|
||||
LLM usage results in massive security holes.
|
||||
|
||||
* [Meta Security Researcher's AI Agent Accidentally Deleted Her Emails](http://archive.today/2026.02.26-153034/https://www.pcmag.com/news/meta-security-researchers-openclaw-ai-agent-accidentally-deleted-her-emails)
|
||||
* [Moltbook's "vibe-coded" breach is the future of security failures](https://thehill.com/opinion/cybersecurity/5744310-ai-powered-security-risks/)
|
||||
* [In a study evaluating over 500k code samples, LLM-generated code was found to contain more high-risk security vulnerabilities than human-generated code](https://arxiv.org/abs/2508.21634)
|
||||
* [LLMs make up package names, making them vulnerable to incorporating malicious code in "slopsquatting" attacks](https://www.theregister.com/2025/04/12/ai_code_suggestions_sabotage_supply_chain/) ([Arxiv study](https://arxiv.org/abs/2406.10279))
|
||||
|
||||
## What You Can Do
|
||||
|
||||
I'd like to kindly suggest implementing a strict "No AI" policy. This can also help with what seems to be larger and larger influxes of low quality drive-by PRs by AI agents.
|
||||
|
||||
You can find other projects that have taken steps to say no to AI here:
|
||||
https://noai.starlightnet.work/list.html
|
||||
|
||||
For a specific policy, I can recommend the following policies for inspiration:
|
||||
|
||||
- [wafrn's Contributring Doc](https://codeberg.org/wafrn/wafrn/src/branch/main/CONTRIBUTING.md)
|
||||
|
||||
- [Loupe's Use of Generative AI Policy](https://discourse.gnome.org/t/loupe-no-longer-allows-generative-ai-contributions/27327)
|
||||
|
||||
Thank you and kind regards :pray:
|
||||
```
|
||||
## Appeal to Fear of Legal Ramfification Template
|
||||
```markdown
|
||||
Hello,
|
||||
|
||||
I'd like to talk about your AI policy. Below are some reasons why using AI can result in legal trouble in the future:
|
||||
|
||||
## Legal Ramifications
|
||||
|
||||
LLMs are often trained on, and thus prone to regurgitate (either completely, or in-part), chunks of code that are licensed under terms which have specific legal requirements that a contributor using LLMs may not understand or even be aware of when making a contribution. Regardless of this ignorance, it falls to the repo's owner to comply with the terms of any and all licensed code integrated into their project.
|
||||
|
||||
### License Problems
|
||||
|
||||
Legal, copyright, and ethics problems arise, especially with copyleft licenses such as the GNU (A/L)GPL. With the "help" of AI the copyleft code may be "license-washed" very easily.
|
||||
|
||||
Here are some ongoing problems with AI "license-washing" in the FOSS world:
|
||||
|
||||
* `chardet` - used an LLM to rewrite the codebase from the LGPL license to Expat/MIT (and later 0-BSD) license, violating the (L)GPL.
|
||||
* relicensed release: <https://github.com/chardet/chardet/releases/tag/7.0.0>
|
||||
* original author's concerns: <https://github.com/chardet/chardet/issues/327>
|
||||
* "consumer's" concerns: <https://github.com/chardet/chardet/issues/331>
|
||||
|
||||
Additionally, there have been legal cases regarding the usage of AI:
|
||||
|
||||
* [GitHub Copilot litigation](https://githubcopilotlitigation.com/)
|
||||
* [IEEE article explaining concerns about AI generated code ownership](https://spectrum.ieee.org/ai-code-generation-ownership)
|
||||
* [Tracker of broader lawsuits against AI companies](https://chatgptiseatingtheworld.com/2025/11/02/tracker-of-tort-lawsuits-v-ai-companies/)
|
||||
|
||||
### Stolen Training Data
|
||||
|
||||
AI companies use data from across the web to train their models, most often without the website owners' and users' consent. Big tech companies like Google and Meta are scraping data from the users of major FOSS projects, such as Mastodon, WordPress, and other ActivityPub-powered and self-hosted software.
|
||||
|
||||
* In 2023, [the Washington Post published a list of sources in Google's C4 data set](https://archive.ph/eehKq). A multitude of fediverse instances and personal sites were included. The fediverse is known for its userbase being major proponents of privacy and opt-in consent, making this especially jarring for those who have chosen to use decentralized social media for control over their data.
|
||||
* In 2025, [a similar leak of Meta's sources was published](https://archive.ph/NZlf3). Meta's list demonstrates how their integration of ActivityPub into their Threads software has enhanced their ability to scrape content without authorization. Threads is widely blocked in some parts of the fediverse, but their scraping of server CDNs has allowed them to get around that. Notably, both the CDN domains of the managed hosting services masto.host and fedi.monster are included in the list; large servers like mastodon.art, which is hosted by the former and has many artists who've left sites like DeviantArt and others due to their AI scraping of user content, had [media unknowingly scraped](https://mastodon.art/@Curator/115022115346692178).
|
||||
* In March 2026, [a research paper](https://arxiv.org/html/2603.20957v2) showed that simply fine-tuning LLMs resulted in outputs containing up to 90% of entire (copyrighted) books, contradicting LLM companies' previous statements in court that their models do not store copies of training data. After fine-tuning exclusively on a single author, the researchers were able to cause the LLM to output works from over 30 completely unrelated authors across different genres. None of the models were explicitly trained on these books by the researchers, which indicates that LLMs always carry with them a considerable amount of copyrighted materials from training.
|
||||
|
||||
Usage of AI in your project is usage of tooling that blatantly disregards licensing and violates the Code of Conduct in your project (if present), making said tools antithetical to FOSS' purpose.
|
||||
|
||||
## What You Can Do
|
||||
|
||||
I'd like to kindly suggest implementing a strict "No AI" policy. This can also help with staying your code legally clean as code by AI agents often ignore licensing requirements.
|
||||
|
||||
You can find other projects that have taken steps to say no to AI here:
|
||||
https://noai.starlightnet.work/list.html
|
||||
|
||||
For a specific policy, I can recommend the following policies for inspiration:
|
||||
|
||||
- [wafrn's Contributring Doc](https://codeberg.org/wafrn/wafrn/src/branch/main/CONTRIBUTING.md)
|
||||
|
||||
- [Loupe's Use of Generative AI Policy](https://discourse.gnome.org/t/loupe-no-longer-allows-generative-ai-contributions/27327)
|
||||
|
||||
Thank you and kind regards :pray:
|
||||
```
|
||||
28
STYLE.md
28
STYLE.md
|
|
@ -1,6 +1,6 @@
|
|||
# Style Guide
|
||||
|
||||
This is a guide for how to structure the markdown tables and headings of the main README.md of this repo. Please be sure to organize the categories alphabetically to save people time in finding things within the list.
|
||||
This is a guide for how to structure the markdown tables and headings of the main README.md of this repo.
|
||||
|
||||
* [Tainted Software](#tainted-software)
|
||||
* [Category](#category)
|
||||
|
|
@ -12,26 +12,21 @@ Be sure to put things in the correct category and always update the above TOC (t
|
|||
|
||||
## Category
|
||||
|
||||
Make sure to format your table like below (note that it is alphabetized by software name):
|
||||
Make sure to format your table like below:
|
||||
|
||||
| Name | Last Untainted Version or Commit ID | Tags and Evidence | Alternative(s) |
|
||||
|---|:---:|---|---|
|
||||
| [formallyCoolSoftware](https://linktocoolsoftware.tld) | [`ab12345`](linktolastgoodcommitid.tld/commit/ab12345) | [](https://codeberg.org/small-hack/open-slopware#ai-functionality) ([1](https://docs.linktocoolsoftware.tld/ai-assistant))<br/> [](#permissive-ai-policy) ([1](https://linktocoolsoftware.tld/branch/main/AGENTS.md))<br/> [](https://codeberg.org/small-hack/open-slopware#ai-code-reviews) ([1](https://linktocoolsoftware.tld/branch/main/AGENTS.md))<br/> [](https://codeberg.org/small-hack/open-slopware#gen-ai-art) ([1](https://linktocoolsoftware.tld/ai_logo.jpg))<br/> [](https://codeberg.org/small-hack/open-slopware#ai-databroker-usage) ([1](https://linktocoolsoftware.tld/privacypolicy)) <br/>  ([1](https://linktocoolsoftware.tld/branch/main/README.md)) <br/> [](https://codeberg.org/small-hack/open-slopware#ai-in-issue-tracker) ([1](http://linktocoolsoftware.tld/issues/123))<br/> [](https://codeberg.org/small-hack/open-slopware#permits-llm-ingestion) ([1](https://linktocoolsoftware.tld/branch/main/ai_policy.md)) | [coolSlopFreeProject] |
|
||||
| [formallyOKSoftware](https://linktofinesoftware.tld) | [`v2.0.0`](linktolastgoodversion.tld/v2.0.0) | [](#permissive-ai-policy) ([1](https://linktocoolsoftware.tld/branch/main/AGENTS.md))<br/>  ([1](https://linktocoolsoftware.tld/branch/main/README.md))| [alrightSlopFreeProject] |
|
||||
| [formallyCoolSoftware](https://linktocoolsoftware.com) | [`v2.0.0`](linktolastgoodversion.com/v2.0.0) *or* [`ab12345`](linktolastgoodcommitid.com/commit/ab12345) | [](#permissive-ai-policy) ([1](http://linktocoolsoftware.com/branch/main/AGENTS.md))<br/>  ([1](http://linktocoolsoftware.com/branch/main/README.md))| [coolSlopFreeProject] |
|
||||
|
||||
**Evidence column**: should contain one or more of the following tags (followed by *up to 3* numbered evidence links in parentheses):
|
||||
|
||||
- [](https://codeberg.org/small-hack/open-slopware#ai-functionality)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#permissive-ai-policy)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#ai-code-reviews)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#sponsored-by-ai)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#gen-ai-art)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#ai-databroker-usage)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#sponsored-by-ai)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#ai-in-issue-tracker)
|
||||
- [](https://codeberg.org/small-hack/open-slopware#permits-llm-ingestion)
|
||||
|
||||
> [!note]
|
||||
> The above order is the official order you should add your tags in.
|
||||
|
||||
**Don't know what the alternative or last known good version is?** Use this badge in its place:
|
||||
|
||||
|
|
@ -56,19 +51,15 @@ Here are all the badges for easy copying and pasting:
|
|||
```
|
||||
|
||||
```markdown
|
||||
[](#gen-ai-art)
|
||||
[](https://codeberg.org/small-hack/open-slopware#gen-ai-art)
|
||||
```
|
||||
|
||||
```markdown
|
||||
[](#ai-databroker-usage)
|
||||
[](https://codeberg.org/small-hack/open-slopware#ai-databroker-usage)
|
||||
```
|
||||
|
||||
```markdown
|
||||
[](#ai-in-issue-tracker)
|
||||
```
|
||||
|
||||
```markdown
|
||||
[](#permits-llm-ingestion)
|
||||
[](https://codeberg.org/small-hack/open-slopware#ai-in-issue-tracker)
|
||||
```
|
||||
|
||||
```markdown
|
||||
|
|
@ -92,6 +83,5 @@ The above "Alternative(s)" column is for software that has a 1:1 parity or is a
|
|||
> * [coolSlopFreeProject]: This can be a short description and [link to anti-AI policies](somelink.link).
|
||||
|
||||
<!-- here is where you would put your links to alternative software, to keep the markdown doc clean -->
|
||||
[alternativeSoftware]: https://verygoodnotslopware.tld "alternative software"
|
||||
[coolSlopFreeProject]: https://verygoodnotslopware2.tld "another alternative software"
|
||||
[alrightSlopFreeProject]: https://veryoknotslopware3.tld "another extra alternative software"
|
||||
[alternativeSoftware]: https://verygoodnotslopware.com "alternative software"
|
||||
[coolSlopFreeProject]: https://verygoodnotslopware2.com "another alternative software"
|
||||
|
|
|
|||
|
|
@ -1,19 +0,0 @@
|
|||
<svg xmlns="http://www.w3.org/2000/svg" width="123" height="20" role="img" aria-label="Permits LLM Ingestion">
|
||||
<title>Permits LLM Ingestion</title>
|
||||
<linearGradient id="s" x2="0" y2="100%">
|
||||
<stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
|
||||
<stop offset="1" stop-opacity=".1"/>
|
||||
</linearGradient>
|
||||
<clipPath id="r">
|
||||
<rect width="123" height="20" rx="3" fill="#fff"/>
|
||||
</clipPath>
|
||||
<g clip-path="url(#r)">
|
||||
<rect width="0" height="20" fill="#525252"/>
|
||||
<rect x="0" width="123" height="20" fill="#525252"/>
|
||||
<rect width="123" height="20" fill="url(#s)"/>
|
||||
</g>
|
||||
<g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
|
||||
<text aria-hidden="true" x="617" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="1130">Permits LLM Ingestion</text>
|
||||
<text x="617" y="140" transform="scale(.1)" fill="#fff" textLength="1130">Permits LLM Ingestion</text>
|
||||
</g>
|
||||
</svg>
|
||||
|
Before Width: | Height: | Size: 1,003 B |
BIN
evidence/img/vscode.png
Normal file
BIN
evidence/img/vscode.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 373 KiB |
BIN
evidence/img/zbus.png
Normal file
BIN
evidence/img/zbus.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 98 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 274 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 121 KiB |
Loading…
Add table
Add a link
Reference in a new issue