TL;DR
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
QGIS merged QEP-428 on Oct. 7, prohibiting LLM-, AI- or agent-assisted code contributions to the qgis/qgis repository. The proposal replaces an earlier policy based on human review and disclosure; its author said the project may consider limited exceptions later.
The QGIS project has merged a proposal barring AI-assisted code contributions to its main repository, replacing a previous policy that permitted AI use under human review and disclosure rules. The change, known as QEP-428, was merged into the QGIS Enhancement Proposals repository on Oct. 7.
QEP-428 states that LLM-, AI- or agent-assisted code contributions are not allowed in the qgis/qgis repository. It warns that if the project later discovers AI or agent assistance was used, the contribution may be reverted and the contributor may face sanctions affecting their project rights.
The proposal was authored by QGIS core contributor Nyall Dawson. The pull request passed its discussion period on Oct. 5, proceeded to a vote and was merged two days later. The source record confirms the proposal’s status and wording; it does not establish that any contributor has been sanctioned under the new rule.
QEP-428 replaces QEP-408, which had set a human-in-the-loop approach: contributors were expected to review AI-generated output, disclose assistance using “Assisted-by” trailers, and avoid unreviewed agent comments. Dawson wrote in the discussion that the required process had not been followed in practice.
A Stricter Rule for QGIS Code
The change gives contributors a clearer but more restrictive standard for submitting code to a widely used open-source geographic information system. Under the prior policy, AI assistance could be used if people reviewed the output and disclosed it. The new text instead sets a prohibition for code contributions to the named repository, backed by possible reversions and contributor-rights sanctions.
That distinction matters as software projects decide how to handle code produced or shaped by generative AI tools. QGIS’s decision puts the burden on contributors to avoid AI-assisted code submissions, while leaving project maintainers to interpret and enforce the rule. It may also affect contributors who use AI features integrated into development tools, though the proposal’s practical boundaries are not fully detailed in the source material.
Dawson said the project had already lost at least one “extremely high value” contributor as a result of the earlier policy. That is Dawson’s account of the policy’s effects, not an independently documented finding in the available proposal record. It indicates that the project’s governance debate includes both compliance concerns and the effect of its rules on participation.
As an affiliate, we earn on qualifying purchases.
From Disclosure to Prohibition
The previous QGIS policy, QEP-408, was adapted from the LLVM AI Tool Use Policy, according to the QEP-428 discussion. It attempted to permit assistance while requiring contributors to check AI output and identify its use. One stated restriction was against unreviewed comments generated by agents.
In the QEP-428 discussion, Dawson argued for beginning with a closed-door approach and potentially allowing specific uses later, citing autocomplete-style assistance and translations as examples that could be considered separately. The proposal’s merged text, however, states a broad prohibition on AI-assisted code contributions. The source material does not describe a separate, adopted exception for those examples.
The proposal’s Oct. 7 merge was its formal project milestone. The available record says public visibility followed through a Hacker News submission on Oct. 12; that later attention is not the date the policy was merged.
“No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.”
— QEP-428, merged proposal
AI-assisted coding tools for developers
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Enforcement and Exceptions Remain Open
The proposal does not spell out how maintainers will determine whether code was AI-assisted, what evidence would be used, or how sanctions would be decided. The source material also does not identify any contribution already reverted under the new rule or any contributor rights already restricted.
It is also unclear how the project will treat borderline cases, such as AI features embedded in editors or tools used for translation rather than code generation. Dawson mentioned possible case-by-case openings, but the merged proposal contains a prohibition and does not define a process for granting exceptions. The material does not establish whether further guidance has since been issued.
As an affiliate, we earn on qualifying purchases.
Watch for Implementation Guidance
The next developments to watch are any implementation guidance from QGIS maintainers, decisions on how the rule applies to particular tools, and any later proposal introducing defined exceptions. The available source record gives no schedule for such guidance or for a future policy review.
For contributors, the operative text is the merged QEP-428 policy: AI-, LLM- and agent-assisted code contributions are prohibited in the qgis/qgis repository, with possible reversion and contributor-rights consequences if use is discovered. Whether the project will refine enforcement or add limited allowances remains unresolved.
geographic information system software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did QGIS change?
QGIS merged QEP-428, which prohibits AI-, LLM- or agent-assisted code contributions to the qgis/qgis repository. It replaces an earlier policy that allowed assistance subject to human review and disclosure.
When was the proposal adopted?
QEP-428 was merged into the QGIS Enhancement Proposals repository on Oct. 7, 2026, after passing its discussion period and moving to a vote.
What could happen if AI use is discovered?
The proposal says the contribution may be reverted and the contributor may face sanctions affecting their project rights. The available source does not report a case in which those measures have been applied.
Are there exceptions for autocomplete or translation?
Dawson mentioned those as examples of uses the project might consider allowing case by case later. The merged proposal does not establish an adopted exception or set out a process for approving one.
Source: hn
Columbus Day / Indigenous Peoples' Day Picks
long weekend sales
As an affiliate, we earn on qualifying purchases.
