Skip to content

Instantly share code, notes, and snippets.

@webknjaz
Last active August 22, 2026 19:34
Show Gist options
  • Select an option

  • Save webknjaz/1819dd466cc908ff09e2ed4d934455eb to your computer and use it in GitHub Desktop.

Select an option

Save webknjaz/1819dd466cc908ff09e2ed4d934455eb to your computer and use it in GitHub Desktop.
EuroPython 2026: Defending Open Source from "AI" Slop: A Maintainer's Practical Guide

Defending Open Source from "AI" Slop — links

Companion references for the EuroPython 2026 talk by Sviatoslav Sydorenko (@webknjaz) · Friday, 17 July 2026, Room S1. Slides and the recording will appear on the session page: https://ep2026.europython.eu/session/defending-open-source-from-ai-slop-a-maintainer-s-practical-guide

Assisted-By: Claude:claude-fable-5 claude-code marp — this talk discloses itself; so does this document.

The policy template (adapt, don't copy blindly)

The configuration files

The in-depth discussion behind the rules

Case studies mentioned in (or cut from) the talk

Surveys of the policy landscape

Attribution formats (if you want structure)

Etiquette for humans

Support this work

@webknjaz

Copy link
Copy Markdown
Author

@webknjaz

Copy link
Copy Markdown
Author

Started experimenting with in-project “behave yourself” agent context: ansible/pylibssh#867. It's probably not something that should be copied into every project but be centralized. Though, how do we force the poor-behaved spammers follow the rule of non-slop? They should come in and act according to the house rules!
Also, I feel like https://snipe.net/2014/11/05/how-to-contribute-to-open-source-without-being-a-dick/ should be a part of the game, maybe?

@webknjaz

Copy link
Copy Markdown
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment