1
0
Fork
You've already forked template
0

Add an AI policy #3

Closed
opened 2026年06月20日 15:21:03 +02:00 by MultisampledNight · 4 comments

Inspiration:

- *Make sure **no** generated code ends up in repo or in nonquarantined communications.* Contributions with generated code/docs/comms will be treated like a formal problem as per [SFC LLM-gen-AI recommendation 3](https://sfconservancy.org/llm-gen-ai/llm-backed-generative-ai-recommendations.html), i.e. responded to with kindness and rejected - Inform users of the harm they are perpetuating by using LLMs (possibly make them watch https://www.youtube.com/watch?v=olhu9UhFGl4) - Overview: https://blog.johanneslink.net/2025/11/04/to-gen-or-not-to-gen/ - Human rights violations: https://www.amnesty.org/en/documents/pol40/0996/2026/en/ - Economic harm: https://www.mcsweeneys.net/articles/ai-economics-for-dummies, https://www.wheresyoured.at/the-case-against-generative-ai/ - Social harm: https://nicolasbouliane.com/blog/death-by-ai, https://joshcollinsworth.com/blog/sloptimism, https://www.garfieldtech.com/blog/selfish-ai - Most software is safety critical: https://www.softwaremaxims.com/blog/we-should-have-caught-it - Epistemic harm: https://ergosphere.blog/posts/the-machines-are-fine/, https://dl.acm.org/doi/10.1145/3442188.3445922 - If despite this, they want to use them anyway, force the LLM to act in a TA-only mode. Make the user write *all* code (other than bare symbol autocompletion) and puncture their understanding at times (see also https://htmx.org/essays/universities-and-ai/) - If a user can give a convincing argument as for how using an LLM generatively reduces a disability barrier for them, have them get in touch with the repository maintainer via social private mention or email. Inspiration: - Language to pick - imagine you're talking to a neoliberal: https://unstable.systems/@AmyZenunim/116672510693285709 - use pseudo-reasoning shortcuts: https://needtoknow.fyi/card/shortcut-reasoning/ - What Carson Gross uses; probably still too lax: https://gist.github.com/1cg/a6c6f2276a1fe5ee172282580a44a7ac - https://github.com/DrCatHicks/learning-opportunities

I don't want to ban AI overall. We, as a generation of antifascists, mustn't fall into a "generational blunder": https://www.youtube.com/watch?v=lRq0pESKJgg

I am not a friend to the technofascists. I am exactly the demographic that they are trying to make disposable. But I'm afraid that if we aren't careful with how we critique the use and abuse of artificial intelligence, we might end up, as leftist philosopher Mark Fischer once warned, foreclosing the possibility of a technologized anti-capitalism. I fear that framing this debate as anti-tech versus pro and handing the pro tech position to the right-wing is a generational blunder. (5:31)

Hating AI for the wrong reasons isn't just a philosophical blunder, but the first step down a path that may end up hurting the very people we vowed to protect. (1:12:25)

I do think that using AI for narrow tasks is useful. I also think that an introspective instead of generative approach could be genuinely valuable for swdev (I think the point of writing FOSS is to collectively learn to write better code and systems, not to actually have a product, hence I also think that categorically denying generative use is defensible).

I don't want to ban AI overall. We, as a generation of antifascists, mustn't fall into a "generational blunder": https://www.youtube.com/watch?v=lRq0pESKJgg > I am not a friend to the technofascists. I am exactly the demographic that they are trying to make disposable. But I'm afraid that if we aren't careful with how we critique the use and abuse of artificial intelligence, we might end up, as leftist philosopher Mark Fischer once warned, foreclosing the possibility of a technologized anti-capitalism. I fear that framing this debate as anti-tech versus pro and handing the pro tech position to the right-wing is a generational blunder. (5:31) > Hating AI for the wrong reasons isn't just a philosophical blunder, but the first step down a path that may end up hurting the very people we vowed to protect. (1:12:25) I do think that using AI for narrow tasks is useful. I also think that an introspective instead of generative approach could be genuinely valuable for swdev (I think the point of writing FOSS is to collectively *learn* to write better code and systems, not to actually have a product, hence I also think that categorically denying generative use is defensible).

How other projects are doing it:

How other projects are doing it: - Godot: https://godotengine.org/article/contribution-policy-2026/ - See https://github.com/rust-lang/rust-forge/pull/1040 description section `Prior art`

After reading https://doi.org/10.1007/s00146-023-01710-4: This issue and #2 are the exact same, just different perspectives on "what values do we follow in this project". We don't need to look for primordial argumentation on why or why not LLMs could ever develop, because that is irrelevant at this stage: We care about ethics and politics, first and foremost, and metaphysics somewhere after that. We can absolutely construct values to use as root for metaphysics

After reading https://doi.org/10.1007/s00146-023-01710-4: This issue and #2 are the exact same, just different perspectives on "what values do we follow in this project". We don't need to look for primordial argumentation on why or why not LLMs could ever develop, because that is irrelevant at this stage: We care about ethics and politics, *first and foremost*, and metaphysics somewhere *after* that. We can *absolutely* construct values to use as root for metaphysics

Hence closing in favor of #2

Hence closing in favor of #2
Sign in to join this conversation.
No Branch/Tag specified
next
release
No results found.
Labels
Clear labels
0-Status
0-Backlog
Can be picked up if so desired.
0-Status
1-Blocked
Cannot progress at the moment due to an external dependency (outside of this repository).
0-Status
2-Planned
Aim to do next sprint.
0-status
3-Todo
Aim to do this sprint.
0-Status
4-Progressing
Working on that in this very moment.
0-Status
5-Feedback desired
Please take a look and review. Can be done by anyone, including you!
0-Status
Needs triage
Please assign more fitting labels and give an initial response.
1-Priority
0-Frozen
Not a factor right now.
1-Priority
1-Low
Keep on radar, do if enough time emerges.
1-Priority
2-Medium
Want to do this in the mid-term.
1-Priority
3-High
Do this in the short-term.
1-Priority
4-Critical
Do this as soon as possible.
2-Complexity
1-Low
Should not have any complications. Straightforward. Often "dull" chores.
2-Complexity
3-High
Deeply intertwined and nested.
3-Area/Code
3-Area/Communication
Exchanging information and talking with others. Beep boop.
3-Area/Design
Planning and thinking about user interactions.
3-Area/Documentation
Writing down processes and emergence of the status quo.
3-Area/Meta
Informative (not actually an issue).
4-expertise/Accessibility
Removing barriers, comprehending the intricacies of interfaces.
4-expertise/Security
Catching assumptions and fixing loopholes.
5-stakeholder/Add a stakeholder here
5-type
Bug
Something doesn't work as expected.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
MultisampledNight/template#3
Reference in a new issue
MultisampledNight/template
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?