← Back to context

Comment by basch

1 day ago

All these projects should seamlessly run a fork in parallel that accepts AI and has AI for review and approval. Both camps are happy.

Basically a play sandbox for contributors to not get jaded. A honeypot to contain the verbosity vomit, while also serving as positive public relations by keeping young contributor morale from starting in the basement.

Everyone has been that person once early in their life who is told they aren’t welcome and never comes back. Maybe it was SourceForge or IRC, maybe it was Wikipedia.

What's the point of this fork if it's just a landing spot for stuff that's not really wanted? Wouldn't that just be more condescending then telling people what's actually required for a contribution? Besides, the nature of forking is you can just do it yourself anyway. If people love their AI changes they can just make their own fork.

Plus I don't know how you could do this "seamlessly" -- someone has to manage merge conflicts, and as the codebases diverge it's just going to get more and more gnarly. (this is the reason most people don't maintain their own forks in the first place)

Do you volunteer to maintain the sloppy fork?

  • I think most pro-AI people would be happy to let an AI maintain the sloppy fork. What reason would they have to complain, after all?

This is actually a good idea.

I mean, not sure if everyone wants that for their project, and there will surely be plenty of trade-offs.

But it would be a very good compromise: You (the maintainer) get only human-generated PRs in the canonical project, and they (pro-AI contributors) get a lower-threshold sandbox to play with. Best case scenario, you cherrypick the pre-filtered golden nuggets to bring back to the canonical project.

  • Precisely. Cherrypick nuggets from poo. It's there if you care to wade into it. May occasionally strike gold.