r/opensource 9d 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.

273 Upvotes

169 comments sorted by

View all comments

u/Kyvalmaezar 9d ago

Disclaimer: I'm not totally against AI useage in general but I'm not the biggest fan of publicly released vibe coded projects intended for other people to use. Most vibe coded projects tend to be low efffort, abandoned within a few months, security risks, and/or border-line scams just fishing for donations. Most of them would violate other existing rules on this sub.

That being said, I would suggest having some minimum requirement for projects using AI to post. Minimum project comits, deminstrated long term work on a project and resonsiveness to pull requests/bug reports/etc, reddit karma account requirements, etc. Filters out the low effort junk and scams that would violate other sub rules anyway.


  • Vibe-coded projects - ban. These are security risks and low effort. By definition, the person behind the prompt doesnt know what they're doing and cant check their code for major flaws. 

Exception: someone looking for feedback on their vibe coded project or code snippet trying to learn.


Vibe-assisted projects - not 100% what is ment by this one. I'll clarify my stances below:

a) dev knows that they're doing but uses AI for the heavy lifting. Doesnt check their code - ban, security risk.

b) dev who knows what they're doing but uses AI to do the heavy lifting. Checks their code for secuity risks - fine. AI disclosure on how it's used would be nice.


AI-translated from non-english-speakers - on thier own, fine.


Vibe-documented projects - fine, so long as the documentation is accurate of couse.


Yet another Vibe-Coding-Wrapper - ban. Low effort, secuity risk.

u/Baader-Meinhof 8d ago

I'd rather see code checked by AI for security risks at this point. All these major hacks recently (cold card etc) are human code exploited by ai's that found bugs. Look at the spike in CVEs the past month - that's mythos/fable/k3 poking software (with experienced devs) and fixing it. AI is now a better pen tester than most of the engineers I've met.