HortusFox Anti AI Enforcement for Pull-Requests

I've been thinking about this for a while now, but I've postponed a decision multiple times, as it sounded too strict to me at first. But now it's here.

I've decided to employ a radical Anti AI Enforcement Policy for HortusFox

There are various issues with AI, especially vibe-coding, which I've already outlined in this article (please read it if you haven't already). And while AI slop code was easily recognizable when LLMs first came out, it's getting harder and harder. HortusFox is a pure work of human imagination, creativity and connection with nature. AI is neither. I'm very concerned about pull requests beeing merged that were created using Claude, ChatGPT, Copilot or other AI tools. In addition to the dangers of vibe-coding mentioned in said article, I strongly oppose big tech corporations being intertwined in my products. This would be the way to loose control over your own work, essentially contributing to a shift where software developers merely become management minions of AI slop. I don't want this, and I know that this will be the kind of singularity where we destroy our natural passion. And allowing AI generated code in HortusFox would essentially be a contribution to this change while even silently handing over the responsibility and ownership to AI companies. 

Hence I've decided to employ this policy. But wait, you've already enforced this in the contribution guidlines, right?

That's correct!

But I've now also decided to generally deny pull requests for an indefinite amount of time. All current pull requests will be closed.

I know this may sound unfair to existing PRs, but I don't see any other way. It's hard for me to examine what PR is entirely vibe-coded, partially vibe-coded or AI assisted due to how AI advanced in the last two years. Usually, especially when starting as a project, you don't really know the people who submit PRs. And given that HortusFox is based on a custom PHP framework, the contribution barrier is higher than compared to other projects that use a well-established framework. But AI is now at a point where it can produce code even when a project is built upon a custom framework while the code is even more prone to all possible flaws. 

So, how can I possibly know what PR to close and what to permit? It's a labor that I am not willing to do as I've got better things to do, honestly. I want to focus on my work and other issues, I don't want to be a "gatekeeping PR manager". Hence, the only viable solution is to deny PRs alltogether, and see how things will turn out.

I am sorry for all PRs that are currently open, I appreciate the work behind your PRs, but given the current situation with AI, I don't see any other way around this.

I really hope that we - the people - will realize that we are not victims of an "evolutional change". We decide what we want to do. We need to take back our power from large corporations. Because AI will essentially contribute to enshittifcation (it already does), and it will make companies even more rich, while the working people will once again be left behind.

Thank you for reading.