I imagine that their issue is reviewer bandwidth.

If all submissions were high-quality, it would probably work. But that is probably unlikely.

Maybe the project could host a searchable directory of AI contributions hosted at external GitHub repos or something.

My understanding is that the AI policy is more to do with issues of copyright and code provenance. They want to make sure that all of their code is cleared with no risk of accidentally using 'stolen' code or GPL code repeated by an AI. I can at least understand the policy.

I think there's other opinions around AI use there as well, but I'll back off from that. I didn't mean for my post to become top voted, when we should be celebrating Haiku reaching Beta 6. I'm just disappointed that for me, R1/b6 has been a very big regression, right at a time when I've been using AI to make all the software I write cross-compatible with Haiku via Go & SDL, and even use AI to write drivers so more of my hardware works on Haiku... and instead, now I can barely even boot the system.

> I imagine that their issue is reviewer bandwidth.

This feels to me as the real bottleneck in general. Maybe along with thinking through what to code/prompt.

I don't need more tokens or automated generation of PRs, I'm already at capacity for the care and understanding I want to have for code I own.