That's just misattribution and banning AI-generated contributions is, frankly, lazy and stupid. Contributions being AI-generated is not the issue!

The issue are low-quality contributions and there are a lot more of those because AI has made it easier for less qualified coders to tackle more and harder problems. Now, I understand the maintainers who just filter by "AI-generated" do it because it is a simple heuristic that is easy to apply and a quick stop-gap solution to an immediate problem. But this can only be a starting point to develop a better way to handle low quality input. Turning this into a fundamental position is just lazy and stupid.

And to be fair, reading the projects' statements on the website shows that many projects are getting to grips with the new reality and are much more differentiated on the issue as a website called "osssaysno.com" suggests.

▲

crote 2 days ago | parent [-]

> But this can only be a starting point to develop a better way to handle low quality input.

Great! So while the AI vendors are writing free tools to automatically check for low-quality input (surely they are working on that, right?), what do you propose projects do which isn't either banning all obviously-AI contributions due to the good ones being near-impossible to quickly tell apart from slop, or asking volunteers to dig through mountains of shit to find tiny nuggets of gold?

▲

Propelloni a day ago | parent [-]

Nothing changed. Put issues on the queue. Work through the queue in your own time.

Just because your queue grows longer, doesn't mean you have to process more issues in the same time now. It is a FOSS/OSS project, you owe nothing to anybody.

	▲	crote a day ago \| parent [-]
		What changed is that your queue used to be 75% valuable contributions / 20% easy-to-tell garbage / 5% hard-to-tell garbage, but is now 90% hard-to-tell garbage / 5% easy-to-tell garbage / 5% valuable contributions. Your review-minutes-per-merged-contribution has exploded, and your backlog is now growing faster than you can ever dream of processing it. If you don't want to drown, your only option is to do the BigCorp thing of setting it to auto-close after X months and hope important stuff is brought up often enough that it'll catch your eye during the few hours it lives on page 1. You might be okay with this at your day job, but it tends to be a bit of a different story when it is a hobby project you do for fun. > It is a FOSS/OSS project, you owe nothing to anybody. Correct. Which is exactly why many of them are banning AI-generated contributions, and vibecoders shouldn't be complaining about them not being welcomed with open arms.