remote/open-slopware
1
0
Fork 0
mirror of https://codeberg.org/small-hack/open-slopware.git synced 2026-06-01 06:37:06 +02:00
Code Issues Projects Releases Packages Wiki Activity

Merge pull request 'start environment impact section and create CONTRIBUTING.md' (#8) from add-environmental-impact-separate-contributing into main

Browse source 
Reviewed-on: https://codeberg.org/small-hack/open-slopware/pulls/8
Reviewed-by: Max <cloudymax@noreply.codeberg.org>
This commit is contained in:
JesseBot 2026-01-10 19:27:06 +01:00
commit 6e902964f1
2 changed files with 24 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

18
CONTRIBUTING.md Normal file
View file

@ -0,0 +1,18 @@
## Contributing
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 of such (social media posts, screenshots, commit history, links to `CLAUDE.md`, etc). Title the pull request "Add `<software-name>`" or such.
### 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. Accepting drive-by or minor contributions that happen to use LLMs is NOT qualifying. This may change in the future.
2. The software itself integrates genAI features of any kind, internally or externally.
### 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.

27
README.md
View file

@ -6,13 +6,12 @@ The intention of this list is to raise awareness of this technology's usage in p
For more information on why we think this list matters, please see [Why not LLMs?](#why-not-llms).
To Contribute, checkout our [`CONTRIBUTING.md`](./CONTRIBUTING.md).
> [!Note]
> This is a fork of a repo by the same name maintained by the @gen-ai-transparency org on Codeberg. If they up their repo again, we will contribute back.
* [Definitions](#definitions)
* [Contributing](#contributing)
* [Criteria](#criteria)
* [Removal](#removal)
* [Tainted Software](#tainted-software)
* [Browsers](#browsers)
* [Command-Line Shells](#command-line-shells)
@ -37,6 +36,7 @@ For more information on why we think this list matters, please see [Why not LLMs
* [Social Media](#social-media)
* [Why not LLMs?](#why-not-llms)
* [Legal Ramifications](#legal-ramifications)
* [Environmental Impact](#environmental-impact)
## Definitions
@ -48,24 +48,6 @@ For more information on why we think this list matters, please see [Why not LLMs
| sloperator | A person who uses AI prompts to generate anything, typically code or images. |
| slopshop | Company, Organization, or Group of sloperators working together to use AI to generate content. |
## Contributing
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 of such (social media posts, screenshots, commit history, links to `CLAUDE.md`, etc). Title the pull request "Add `<software-name>`" or such.
### 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. Accepting drive-by or minor contributions that happen to use LLMs is NOT qualifying. This may change in the future.
2. The software itself integrates genAI features of any kind, internally or externally.
### 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.
## Tainted Software
### Browsers
@ -214,6 +196,9 @@ Could use some help writing this with concrete receipts on environmental, social
1. 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 sloperator 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.
### Environmental Impact
To start learning a bit more, you can checkout the wikipedia page on [Environmental impact of artificial intelligence](https://en.wikipedia.org/wiki/Environmental_impact_of_artificial_intelligence#Individual_level). We're very open to people contributing other explanations, links, and resources to learn more about this.
<!-- please put your multi referenced links down here -->
[wfree]: https://writefreely.org/