Add QEP428: No ai contributions permitted
QGIS merged a proposal prohibiting AI-assisted code contributions, citing pressure on maintainer review capacity.
TL;DR
- QGIS merged QEP 428 on October 7, changing its contribution policy to prohibit AI-assisted contributions to QGIS repositories.
- The proposal author and supporters cited a rise in review workload and the risk that submitted code would exceed maintainers’ capacity.
- The policy is framed as an initial restrictive rule that may be revisited through later discussion.
QGIS merged pull request 387, titled “Add QEP428: No ai contributions permitted,” into its enhancement-proposal repository on October 7. The pull request records a formal shift from the project’s earlier human-in-the-loop policy to a prohibition on AI contributions. [1] [2]
In discussion, QGIS contributors said AI-assisted submissions had increased pressure on an already limited review group. One maintainer argued that a volume of generated submissions could leave work unreviewed or lead to code being merged without adequate scrutiny. [1] [2]
The discussion also records disagreement about scope. Contributors raised questions about whether the wording covers autocomplete, translation, research, and AI-assisted review; the proposal author said the measure is an initial stopgap that could later be narrowed through separate discussion. [1] [2]
The confirmed change is the policy proposal’s merge, not evidence that every possible use of AI in the development process has been operationally defined. How the project will interpret edge cases and enforce the policy remains open. [1] [2]
Why it matters
QGIS makes maintainer review capacity an explicit constraint on accepting AI-assisted code, turning a fast-growing open-source governance question into a project-level policy.
Editor's note
The headline reproduces the merged GitHub pull-request title. The Hacker News page is linked discussion, not independent reporting; wording about scope follows the public proposal discussion.