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 a proposal on Oct. 7 that prohibits AI, large-language-model and agent-assisted code contributions to the qgis/qgis repository. The policy replaces an earlier disclosure-and-review approach and warns that discovered use may lead to code reversion or contributor sanctions.
The QGIS project has merged a policy banning AI-assisted code contributions to its main repository, qgis/qgis, replacing an earlier approach that allowed AI assistance subject to review and disclosure. The rule, adopted Oct. 7 as QEP-428, says contributions found to have used an AI, large language model or agent workflow may be reverted, and contributors may face sanctions.
QEP-428, titled “No AI contributions permitted,” was proposed by QGIS core contributor Nyall Dawson. The proposal says: “No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.” It also warns that if such use is discovered after submission, the project may reverse the code and sanction the contributor’s rights.
The proposal passed its discussion period on Oct. 5, moved to a vote, and was merged into the QGIS Enhancement Proposals repository on Oct. 7, according to the pull request and its accompanying policy text. The rule is specifically about contributions to the qgis/qgis repository; the available material does not establish that it applies to every QGIS-related project or to all uses of AI outside code contributions.
In the pull-request discussion, Dawson said the project intended to begin with a closed-door policy and might allow specific uses later, such as autocomplete or translations. He also said the prior policy’s process was not happening in practice and that the project had already lost at least one “extremely high value” contributor as a result. Those points are Dawson’s account in the discussion, not independently documented findings in the proposal.
How the Ban Changes QGIS Contributions
The change gives contributors a clearer, stricter rule: AI-assisted code is not permitted in the named repository, even where a human reviews the resulting contribution. The stated consequences make the policy more than a disclosure requirement; they create a risk that accepted code could later be removed and contributor privileges restricted if AI use comes to light.
For maintainers, the decision sets a different standard from projects that permit AI tools with review or labeling. For contributors, it leaves less room to interpret whether assistance is acceptable, while raising practical questions about how the project will identify prohibited use and apply sanctions. The policy’s possible future exceptions could also matter to developers who use AI for narrowly defined tasks, but Dawson described those as possibilities for later consideration, not current allowances.
As an affiliate, we earn on qualifying purchases.
From Disclosure to Prohibition
QEP-428 replaces the earlier QEP-408 AI tool policy, associated with Even Rouault and adapted from LLVM’s AI Tool Use Policy. That approach required contributors to review all output from large language models, disclose assistance through “Assisted-by” trailers, and avoid unreviewed agent comments.
The new proposal says that framework was not working as intended in practice. Its adoption therefore marks a shift from managing and documenting AI use to disallowing AI- or agent-assisted code contributions in the main QGIS repository. The proposal’s recorded discussion and merge dates establish the decision; they do not, by themselves, show how enforcement will work day to day.
““No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.””
— QEP-428, the merged policy text
As an affiliate, we earn on qualifying purchases.
Enforcement and Exceptions Remain Open
The merged text does not specify how QGIS will determine whether a contribution used AI assistance, what evidence would be required, or how sanctions will be chosen. It also does not describe an appeal process or clarify whether the prohibition covers every form of coding assistance, including basic autocomplete. Dawson mentioned autocomplete and translations as examples that could be considered later, but the proposal does not make them exceptions now.
The discussion records Dawson’s statement that the earlier policy had cost the project at least one valuable contributor, but the available material does not identify that contributor or provide further evidence about the circumstances. It is also unclear whether maintainers will publish additional enforcement guidance or revise the policy after observing how it operates.
As an affiliate, we earn on qualifying purchases.
Maintainers Apply the New Rule
The policy is already merged into the QGIS Enhancement Proposals repository. The next practical step is its application to contributions in qgis/qgis. The proposal and discussion do not set a date for a separate implementation milestone or announce a scheduled review.
Any later exceptions would require further action by the project; Dawson presented them as potential case-by-case openings, not changes that contributors can rely on now. Contributors considering code submissions should follow the current prohibition unless QGIS publishes an amended policy or more specific guidance.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did QGIS decide?
QGIS merged QEP-428, which prohibits AI-, LLM- or agent-assisted code contributions to the qgis/qgis repository.
When was the proposal merged?
The discussion period passed on Oct. 5, 2026, and the proposal was merged on Oct. 7.
What can happen if AI use is discovered?
The policy says the contribution may be reverted and the contributor may face sanctions affecting their contributor rights.
Are autocomplete or translation tools allowed?
The merged rule does not list those as exceptions. Nyall Dawson said the project might consider specific uses, including autocomplete or translations, later on a case-by-case basis.
How does this differ from the previous policy?
The earlier QEP-408 policy allowed AI assistance with human review and disclosure. QEP-428 replaces that approach with a prohibition on AI-assisted code contributions to the named repository.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
