SwooshBakery624 [they/them]Vim's lead maintainer has fully lost his goddamn mind
I spent literally all day yesterday working on this:
sciactive.com/human-contribution-policy/
I’ve started to add it to my projects. Eventually, it will be on all of my projects. I made it so that any project could adopt it, or modify it to their needs. It’s got a thorough and clear definition of what is banned, too, so it should help any argument over pull requests.
Hopefully more projects will outright ban AI generated code (and other AI generated material).
PlutoniumAcidI like this approach, but how can it be enforced? Would you have to read every line and listen to a gut feeling?
Basically the best you can do is continue as normal, and if someone submits something that says it is or obviously is AI, point to this policy and reject it. Just having the policy should be a decent deterrent.
If you vibe-code it and use an LLM to respond to reviews, it is really easy to tell.
If you know what you’re doing and just using an LLM to speed up boilerplate writing, honestly who cares. It is technically copyright infringement but so many people are doing it that it’s not likely to be a problem.
I think this policy is overblown a bit. A better policy is “you need to understand, and be responsible for, what every part of your contribution does”. Enough to tell lazy vibecoders to fuck off, and allows for some flexibility in your tooling if you know what you’re doing.