Mandate AI policy for contributions #678
Reference in New Issue
Block a user
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?
Prompted by toolshed/abra#657.
I'm a fan of what Incus does 👍 It's a very practical escape valve and I'd probably have injected a political statement in there somewhere but it hits one of the nails on the head at least. Curious what other people have in mind for this.
https://github.com/manyfold3d/manyfold/blob/main/AGENTS.md
via @3wordchant
love it too, I wouldn't want to review llm generated code (or read any llm generated text, when I want my dose of random words I'll read the billboards on the streets)
I think there are folks in the fed using LLM assisted workflows already. A total ban might not pass as a proposal IMHO, it might be good to have a policy that is more pluralistic.
Here is a bunch of policies if we wanna look at what other projects are implementing: https://github.com/melissawm/open-source-ai-contribution-policies
I've been travelling but I had a notification about AI contributions somewhere for recipes/abra and lost it 🙈 I can't seem to find it now, sorry person who pinged me if/when you see this!
It would be good to take a position on this. To limit the scope of this divisive issue, i would imagine this should happen within the context of the coop cloud federation and its membership, which is ultimately collectively responsible for sustaining the config commons.
An initial poll in the fedi group chat, to sketch out the main lines of agreement/disagreement would be useful. I hope someone can pick this up in the near future.
@decentral1se I started a discussion here:
https://community.coops.tech/t/llms-again-whats-your-take/4903
and asked you here as I didn't know how to reach you :)
ineiti/chat#1
TLDR: I'm an oldtimer (in life and programming), first 3 lines of Basic in 1981 or so. I saw LLMs going from a nuisance (students in a C++ course using them to avoid learning) to change the way I interact with my computer (modifying OSS to fit my needs). I appreciate what coopcloud is doing for people wanting to run their own server, and want to give back... So I'm more on the side of imposing an AGENTS.md and clearly marking LLM generated code, compared to ban it. In the end I want to learn how to use LLMs in a community project!
More prior art:
I'm actually in the search for how to implement what is written in paragraph 5.2 of this: https://arxiv.org/abs/2511.04427:
Of course I understand if you prefer not to be part of that search - and sorry if I didn't make it clear enough when I started opening PRs to abra and several recipes. In that case I'll keep my fork and will not open PRs against the other repos...
The following gives also some indications how to make sure that LLM generated code is helping the projects instead of hurting them: https://allthingsopen.org/articles/open-source-adapt-ai-coding-era-technical-debt
More discussion from the Software Freedom Conservacy:
https://sfconservancy.org/llm-gen-ai/llm-backed-generative-ai-recommendations.html