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 prohibiting AI-, LLM- and agent-assisted code contributions to the qgis/qgis repository. The policy replaces an earlier approach that allowed AI assistance subject to review and disclosure; the proposal says violations could lead to code reversion and contributor sanctions.
The QGIS project has merged a proposal banning AI-assisted code contributions to its main repository, replacing an earlier policy that permitted such work under review and disclosure rules. The proposal, QEP-428, says contributions made with LLMs, AI tools or agent-based workflows are not allowed in the qgis/qgis repository and warns that discovered use could result in code being reverted and contributor rights being sanctioned.
QEP-428 was authored by QGIS core contributor Nyall Dawson and merged into the QGIS Enhancement Proposals repository on Oct. 7, after passing its discussion period on Oct. 5 and moving to a vote. The merged proposal is titled “No AI contributions permitted.” It applies to code contributions to the qgis/qgis repository; the available proposal text does not set out a blanket ban on every use of AI across all QGIS project activity.
The proposal states: “No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.” It adds that if the project later discovers AI or agent assistance was used, contributors may face code reversion and contributor-rights sanctions. Those are consequences described in the policy, not evidence that any particular contributor has already been sanctioned.
The decision reverses the approach in QEP-408, an earlier policy based on LLVM’s AI Tool Use Policy. That policy called for human review of all LLM output, disclosure through “Assisted-by” trailers and a ban on unreviewed comments from agents. Dawson said in the pull-request discussion that the intended process was not happening in practice. He also said the project had lost at least one high-value contributor as a result of the earlier policy.
A New Rule for QGIS Code
The change gives QGIS contributors a clearer, stricter boundary: AI assistance is no longer allowed for code contributions to the named repository, rather than being permitted if reviewed and disclosed. That distinction matters to maintainers, who must apply the rule during contribution review, and to developers deciding whether and how to submit work.
The policy also makes enforcement a project governance issue. Its text allows for reverting code and restricting contributor rights if AI use is discovered, but the available material does not define an investigation process, evidence standard or appeal route. Those details could affect how consistently the rule is applied.
Dawson described the prohibition as a starting point, not necessarily a permanent position. He said the project could consider reopening the door selectively, including for autocomplete or translations. That leaves room for later policy changes, while the present merged rule is the operative development reported here.
As an affiliate, we earn on qualifying purchases.
From Disclosure to Prohibition
QEP-408 took a conditional approach to AI-generated work: contributors could use tools if they reviewed all output and disclosed assistance, while autonomous or unreviewed agent comments were barred. The new proposal replaces that framework with a prohibition on AI-assisted code contributions, rather than adding another disclosure requirement.
The pull request discussion provides the stated rationale. Dawson argued that the earlier policy’s review-and-disclosure process was not happening in reality and said the project had already lost at least one highly valued contributor. These are Dawson’s explanations in the proposal discussion; the source material does not provide independent details about that contributor or quantify how often QEP-408 was followed.
The proposal’s discussion period ended on Oct. 5, before it moved to a vote and was merged two days later. The development was reported publicly on Oct. 12. The change concerns the QGIS project’s own contribution rules, not a general restriction on AI use by QGIS users or developers working outside the repository.
““No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.””
— QEP-428, the merged proposal
As an affiliate, we earn on qualifying purchases.
Enforcement Details Still Open
The merged proposal establishes the ban and names possible consequences, but the available source does not explain how suspected AI use will be assessed, what evidence would be required or how a contributor could challenge a decision. It also does not provide examples of work the project has determined to be in violation.
It is not clear whether the project will publish further implementation guidance, or whether exceptions for uses such as autocomplete and translation will be formally proposed. Dawson’s comments describe possible future reconsideration, but no specific exception is confirmed in the merged rule cited here.
As an affiliate, we earn on qualifying purchases.
How QGIS Applies the Ban
The immediate next step is for QGIS maintainers and contributors to work under the merged QEP-428 policy when submitting and reviewing code for qgis/qgis. The proposal text allows for reversion and contributor-rights sanctions if prohibited assistance is discovered.
Any change to permit particular AI uses would require further action by the project; Dawson’s discussion comment points to possible case-by-case consideration but does not announce a timetable or process. Readers should watch for additional implementation guidance or later policy amendments, which could clarify enforcement and any exceptions.
developer collaboration tools for QGIS
As an affiliate, we earn on qualifying purchases.
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 proposal was merged into the QGIS Enhancement Proposals repository on Oct. 7, 2026, after its discussion period ended on Oct. 5.
What can happen if a contribution used AI?
The proposal says the project may revert the code and sanction contributor rights if it later discovers AI or agent assistance was used. The source does not describe a specific enforcement procedure.
Does the ban cover every use of AI related to QGIS?
The stated rule concerns AI-assisted code contributions to qgis/qgis. The proposal does not establish a general ban on AI use by QGIS users or on every other project activity.
Could QGIS allow some AI uses later?
Dawson said the project could consider opening the policy selectively, with examples including autocomplete and translations. No exception or timetable has been confirmed in the merged proposal described here.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
