>nearly the same amount of effort to post a complaint you can delegate the task of reproducing the issue, diagnosing the root cause, and proposing a fix.

Is the effort the same though?

And even it is the same, making a meaningful contribution to an open source project doesn't mean just fixing your problem, but you also need to stay in line with the contribution guidelines, the project's direction and many more, which takes much more effort than just vibe coding a version for yourself.

Building software for one and for a bunch are two different things. AI is good at the former and can be used for the later but not without much effort. Models will get better, true, but that doesn't mean we need less engineering, in fact we need more to stay up-to-pace with AI. Imagine everyone submitting a PR to fix a bug, how fast can you review it manually? And if you use AI to review/verify them, the cost just shift from person who submitted the PR to the open source maintainer.

That doesn't mean AI is bad but that we need new systems and rules.

That would violate OBS's rules - they disallow AI-written code (or write ups) being submitted. Additionally, if you put nearly the same amount of effort into it as a comment mentioning the original bug - i.e. not much effort - they say that may result in a project ban.

* Appeal to personal responsibility;

* False equivalence.

I'll strike those off my bullshit bingo card.

> All text and content submitted to our project, which includes code, descriptions, issues, and comments, must be human written.

> The use of GitHub Copilot and other assistive AI technologies is heavily discouraged.

> Low-effort or incorrect submissions that are determined to have been generated by, or created with aid of such systems may lead to a ban from contributing to the repository or project as a whole.