QGIS Enacts Strict AI Contribution Ban

QGIS is making a defensible maintainer-capacity bet, but the enforcement boundary remains fuzzier than the headline suggests.

• –The policy responds to AI-generated pull-request volume overwhelming reviewers and weakening confidence in contributor understanding.
• –It reverses QGIS’s earlier human-in-the-loop approach toward a strict code-contribution ban. [Previous policy](https://github.com/qgis/QGIS-Enhancement-Proposals/blob/master/qep-408-ai-tool-policy.md)
• –The rule may filter out low-effort “vibe coding,” but could also catch legitimate uses such as security auditing, brainstorming, or documentation unless clarified.
• –For developers contributing to QGIS, passing tests is no longer enough if AI assistance materially authored the code.
• –The decision signals a broader open-source governance shift: maintainer trust and review capacity are becoming explicit constraints on AI-assisted development.