Hi, On Sat, Feb 21, 2026 at 4:15 PM Marten van Kerkwijk via NumPy-Discussion <[email protected]> wrote: > > > So "No AI contribution is allowed" is a valid take for me if that > > would be the policy. Or "we will use common sense and make opinionated > > decisions, for trivial and otherwise laborious tasks we don't care but > > for involved bits, we won't touch it". It is also fine. > > I'd be happy with either too, with a preference for the second one, > which I see as allowing AI as a tool. > > Disclosure has to be key, though. > > Note that while both would at least somewhat address copyright issues, > only the first would address the pain of having to deal with AI slop. > > To me it remains the bigger problem [1], one I don't see how we can > address without something like a web of trust. But I'll let this be the > last time I note it here, since arguably it is a different discussion, > and also at numpy I'm not one directly affected as I rarely look at new > PRs. Instead, those who do look at new PRs should speak up on whether > they are willing to filter AI slop. But for what it is worth, for > astropy, where I did often look at new PRs, I've concluded that AI slop > is sufficiently shifting the balance towards misery that I will no > longer look at anything unless I'm pinged.
Ouch - yes, that's understandable. Related - Matt Haberland's comment on the Scipy AI policy https://github.com/scipy/scipy/pull/24583#pullrequestreview-3821660783 I wonder whether we'll reach the stage where there are two groups of people in each project that accepts AI-generated code - those who are prepared to review AI-generated PRs, and those who are not. If so, that could unintended effects, as parts of the code become more likely to be AI-generated, parts less, depending on the reviewers. Cheers, Matthew _______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/numpy-discussion.python.org Member address: [email protected]
