Mastodawn

@freecad It should be wise to teach people to use the tools correctly and try to setup manuals on how to do this. Like prompts to clean-up code and add remarks.
In example you could use AI to make the code more readable without changing the code. You can help non-English speakers to add remarks in English etc.

Help users to contribute so you get more and better contributions instead of making it more bureaucratic and difficult.

@MisterMaker @freecad Expecting contributors to understand the changes they are proposing is common sense, not bureaucracy

@prokoudine @freecad More rules=more bureaucracy. I also don't think you can stop this especially if you run an already oversized project as FreeCAD. If you'd split off the addons from main you can probably have a better grip on the code quality. As it's easier to manage.

Aleksandr Prokudin

@MisterMaker @freecad The expectation that contributors understand their code has always been there

@prokoudine @freecad So when I did coding for FreeCAD I got the same remark, but honestly it is a stupid rule, why?
Because there are a lot of devs that put code in FreeCAD then leave and never return, and nobody understands the code that the dev made. Like Realthunder.
So there is a bunch of code that nobody can change because nobody understands it.
It would work if you have like a full-time developer who learns your code before merging.

@MisterMaker @freecad

The remarks you got are that your vibe-coded patches introduce unreadable code that is hard to maintain. You never really addressed that in the several PRs I looked at, and you never resolved conflicts in some of those PRs.

Reviewing badly written vibe-coded patches takes extra time for a relatively small number of maintainers. FC is at an all-time high 470 open PRs and 91 regressions at the moment. Vibe coding is not a solution, it's part of the problem.

[1/2]

@MisterMaker @freecad

Also, let me quote your comment from PR#23793 real quick.

"The @FreeCAD/fpa also doesn't have money to pay devs to do these kind of things.

So they don't want to use the cheap AI stuff and they don't want to pay for it."

This is self-contradictory. Either FC/FPA doesn't have the money or they have it and don't want to spend it. You can pick only one.

Not to mention that reviewing badly written AI code isn't cheap. It's someone else's time.

[2/2]

@prokoudine @freecad It can be both, since code work will have different costs.
Paying someone to rewrite a lot of code, then they don't have the money.
Paying someone to fix small bugs or small features, yes they have the money but they decide to spend it on other stuff.
I should probably join in some FPA meetings and tell all this, but that doesn't sound like fun to me.