OSS is def changing! An increasing number of projects that I follow are taking these types of measures. Some are closing contribs from public; some are refusing patches coded with AI (at least, that's the curious claim). The problem appears agents doing drive-by PRs. When developing my tooling, I had some errant PRs get filed. I already understood the process before I started mixing AI into it, so I knew enough to withdraw them. Lacking experience reviewing and merging, I'd have left those PRs for maintainers to figure out. A practical line in the sand? Some projects require newcomers to submit a good issue and get approval for the PR. That's a slow process in some projects. | I encountered an edge in n8n and put in an issue/PR. Months later I got a "thanks for the correct identification and fix, we wrote it in upstream of your patch". But I dunno what kind of volume you face. In the solution I mentioned, somebody has to review issues and green-light contribs. Will be interesting to watch unfold!

Yeah, I think that looking at the policies of other popular open source projects seems like a good idea! There might be good ideas there.