When will the healing begin with FOSS?
My impression from a distance is that FOSS maintainers are overwhelmed with terrible contributions to the point that anyone trying to contribute is getting locked out. And I get it, repo maintainer is a thankless job.
Big picture, what is the solution? If any maintainer wants to get in on this, how could people actually help? Has anyone put together a good "Vibe do, Vibe don't" guide that is pro-AI? I remember reading an article decades ago about what a good bug report looks like. It was not only extremely technical, but also was clear that if you can't be bothered to write a proper bug report, your report waste time and will go in the garbage because it either isn't actionable or will just waste someone's time chasing a ghost.
So, if I wasn't out of Chatgpt and Claude usage for the week I might ask Claude this question in relation to all the bad photoshop clones people are making fun of.
It is my impression that one of the scars on Gimp is the Qt windowing system. The only thing good you can say about it is that it works on everything. It makes sense at the time it was developed. So, hypothetically, instead of trying to one shot Photoshop terribly, is there some way we could sensibly coordinate on a technical spec for porting / refactoring Gimp to Godot? Maybe a terrible idea, but the great thing about bad ideas is that someone else can give a better idea.
What would it take for a maintainer to maintain a list of "prompts" that people can checkout and return with work completed so if people want to work together constructively and collaboratively it can happen?