[3oil3]

I 100% agree with you, hell, I still don't understand why they didn't merge the thing, if it was beneficial. There is a distinction between noobies comimg up with worthless PR straight copy pasted from an LLM, and that of an unexpected initiative of a user using a sofisticate bot. That's what has been overlooked, it's not a PR from the 'AI', it's a PR from the person using that 'AI'. I don't get all that fear, what the AI going to do now that it filled its context window, besides go 'Actually wait, the user blablabla'

[jmward01]

Directly quoting Scott Shabaugh here:

“Well if the code was good, then why didn’t you just merge it?” This is explained in the linked github well, but I’ll readdress it once here. Beyond matplotlib’s general policy to require a human in the loop for new code contributions in the interest of reducing volunteer maintainer burden, this “good-first-issue” was specifically created and curated to give early programmers an easy way to onboard into the project and community. I discovered this particular performance enhancement and spent more time writing up the issue, describing the solution, and performing the benchmarking, than it would have taken to just implement the change myself. We do this to give contributors a chance to learn in a low-stakes scenario that nevertheless has real impact they can be proud of, where we can help shepherd them along the process. This educational and community-building effort is wasted on ephemeral AI agents.

https://theshamblog.com/an-ai-agent-published-a-hit-piece-on...

[3oil3]

Thanks for the quote. Rules are rules, that's enough of a justification.

[dyauspitr]

In this case because it was a “easy fix” intentionally left in place as an entry point for new contributors.

[jmward01]

Having read the original post and the GH comments about why the PR was denied I was really impressed by their policy. It shows a real effort to develop their community.