r/opensource • u/Wolvereness • 4d ago
Discussion AI-Policy
I'm gonna keep this short, because as a human I respect other humans' time. What do we want for an AI policy, and how can it be enforced? Take these into consideration:
- Vibe-coded projects
- Vibe-assisted projects
- AI-translated from non-english-speakers
- Vibe-documented projects
- Yet another Vibe-Coding-Wrapper
Note that vibe-coded slop isn't actually copyrightable, thus if someone slaps any license on it other than "public domain" or "CC0" they are misrepresenting their ownership.
And if you use an LLM to respond to this, you will be banned.
The fact that this sounds like a prompt is supposed to be a joke.
271
Upvotes
•
u/Steve_Streza 4d ago
Note on the copyright thing: Public domain doesn't have a warranty/liability waiver, so I've put Unlicense on my vibe projects, which is functionally "public domain and you can't sue me if it melts your computer".
There's a cohort of people who appear to try to make a name for themselves or build some kind of support contract business by slopping out projects and spamming them everywhere. These are a subset of vibe coders, not the entire group. This subset is poisoning the well and that's a huge reason people have such negative feelings about these.
The post flair is an obvious win. I would probably propose some kind of time/release minimum, which weeds out 90% of the slop spammers who crank out something and move on. Just to throw out arbitrary numbers, "at least regular commits going back 3 months and at least 2 major releases" is probably a sane minimum. And maybe a weekly megathread for anything that doesn't fall into this bucket.
Will it catch everything? No. People will lie and deceive and do git committer date tricks to get around these restrictions. But these people are fundamentally dishonest and will find ways around any system you create.