### Description of Changes Adds a new merit badge called "🌟 Anti-AI Policy" to distinguish alternatives that take a specific "No AI" stance. - Closes #935 - Changes the badge colors around a bit - "request for help" is now magenta - "ai databroker" is now white - Updates the README.md, STYLE.md, and CONTRIBUTING.md to reflect the change - cleans up the CONTRIBUTING.md file to explain more about adding alternatives - Applies new badge to all projects that had references to Anti-AI policies (and also gotosocial and wafrn) Reviewed-on: https://codeberg.org/ethical-foss/open-slopware/pulls/956
7.9 KiB
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.
Tainted Software
Be sure to put things in the correct category and always update the above TOC (table of contents), so people can easily find your entries. The alternatives heading for each category is only necessary if all items in the category share the same alternatives. More on that below.
Category
Make sure to format your table like below (note that it is alphabetized by software name):
| Name | Last Untainted Version or Commit ID | Tags and Evidence | Alternative(s) |
|---|---|---|---|
| formallyCoolSoftware | ab12345 |
coolSlopFreeProject | |
| formallyOKSoftware | v2.0.0 |
alrightSlopFreeProject amazingSlopFreeProject |
Name column: should be the name of software linked to their git repo (or other software forge if they don't use git).
Evidence column: should contain one or more of the following tags (followed by up to 3 numbered evidence links in parentheses):
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:
Does an alternative you're recommending have an explicit and clear "No AI" policy? Use this special badge to make sure they stand out!
Here are all the badges for easy copying and pasting:
[](#ai-functionality)
[](#vibecoded)
[](#permissive-ai-policy)
[](#ai-code-reviews)
[](#sponsored-by-ai)
[](#gen-ai-art)
[](#ai-databroker-usage)
[](#ai-in-issue-tracker)
[](#condones-llm-ingestion)
[](#request-for-help)
[](#anti-ai-policy)
Important
If a project has multiple tags, please be sure to add a break (
<br />) in between each one, so that the column extends vertically rather than horizontally. This keeps the table visually consistent and easier to read at a glance.
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(es) where this has taken place.
Screenshots are allowed but must be a last resort for something that cannot be linked. We'd prefer archive links in all other instances.
When to use an Alternatives Note Versus Table Column
The above "Alternative(s)" column is for software that has a 1:1 parity or is a very similar alternative specific to the piece of software at hand. If the category or section is filled with the same alternative list (for instance, how it is in the terminal emulators section), you can remove the "Alternatives" column. Instead, you can add a note below the table with all the alternatives, like this:
Note
Category Alternatives
If there are a lot of alternatives for a section, include the alternatives in a note like this. These should also be alphabetized.
- alternativeSoftware:
(1) This can be a short description.
- coolSlopFreeProject: This can be a short description.