Post by @davidism@mas.to

2026-09-18 13:59 UTC

I've turned off pull requests from non-members for Flask, Werkzeug, Jinja, and Click this week, and have enjoyed not waking up to a fresh wave of AI junk every morning. I think I'm going to update our contributing guide to say "introduce yourself and how you use the library in chat first if you want to contribute pull requests". Sad that we had to go here, but aside from conference sprints we weren't really getting outside contribution anyway (which is also sad, but that's been the case a lot longer than AI has been around). #python #flask #opensource

Replies (3)

@paulshryock@phpc.social 2026-09-18 23:25

@davidism@mas.to to be honest, this seems totally reasonable. "If you want to contribute code, let's talk about it first, and here's how to." This is the approach I've also taken with my latest open source project. Not currently accepting pull requests, but plenty of opportunities to talk, and that could lead to opening pull requests to anyone who first talks and has something reasonable to say."

Open ##5329390
@gatesvp@mstdn.ca 2026-09-19 00:01

@davidism@mas.to I'm a regular "drive-by" contributor to OSS. If I find a couple of bugs I will file them. If I think I can fix them I will do that too. Showing up at a meeting to get my code merged is actually something that makes total sense. Especially if it's documented on the contribution guidelines. I think it's also worth noting that it is important for this "all humans" attendance process be accessible. I have had far more bad experiences than good ones when trying to contribute.

Open ##5329402
@leadegroot@bne.social 2026-09-19 00:30

@davidism@mas.to @paulshryock@phpc.social i mean, even ignoring slop, infiltration to insert eg bitcoin generators has long been a problem- this would also help mitigate that!

Open ##5329403