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 bars AI-, LLM- and agent-assisted code contributions to the qgis/qgis repository. The new policy replaces an earlier framework that allowed reviewed and disclosed AI assistance; the proposal says violations may lead to code reversion and contributor sanctions.
The QGIS project has adopted a policy barring AI-, large-language-model- and agent-assisted code contributions to its main repository, replacing an earlier policy that permitted AI use with human review and disclosure. Proposal QEP 428 was merged into the QGIS Enhancement Proposals repository on Oct. 7; it says discovered violations may result in code being reverted and contributor rights being sanctioned.
The merged proposal, titled “No AI contributions permitted,” applies to contributions in the qgis/qgis repository. Its wording prohibits code contributions assisted by an LLM, AI system or agent-based workflow. It also sets out potential consequences if the project later discovers that such tools were used: reversion of the code and sanctions affecting contributor rights.
The proposal was authored by QGIS core contributor Nyall Dawson. The change passed its discussion period on Oct. 5, moved to a vote and was merged two days later. The available proposal and discussion establish the policy decision, though the supplied material does not detail how the project will investigate suspected use or apply sanctions in individual cases.
In the discussion, Dawson said the intention was to begin with a closed-door approach and potentially permit specific uses later, giving autocomplete-like assistance and translations as examples. He also said the previous policy’s review and disclosure process had not been followed in practice, and that the project had already lost at least one contributor he described as highly valuable.
A New Rule for QGIS Contributions
The decision shifts QGIS from managing AI assistance through review and disclosure to prohibiting it for code contributions in the named repository. That gives contributors a clearer restriction, but also places responsibility on them to avoid AI-assisted workflows covered by the policy. The proposed penalties make the change more than guidance about preferred practice.
The rule matters beyond the immediate code review process because it sets a governance choice for an established open-source project: whether AI-generated or AI-assisted work can be accepted under conditions, or should be excluded. QGIS’s discussion also points to a tension between enforcing a consistent contribution standard and retaining contributors who use these tools. The reported loss of a contributor is Dawson’s statement in the proposal discussion, not an independently quantified assessment of the policy’s effects.
As an affiliate, we earn on qualifying purchases.
From Disclosure to Prohibition
QEP 428 replaces QGIS’s earlier QEP-408 AI tool policy. That approach, adapted from the LLVM project’s AI Tool Use Policy, allowed AI-assisted work under conditions: contributors were expected to review all LLM output, disclose assistance through “Assisted-by” trailers and avoid unreviewed agent-generated comments.
The new proposal says those safeguards did not work as intended in practice. Instead of revising the existing review and disclosure requirements, QEP 428 establishes a moratorium on AI-assisted code contributions, while Dawson’s discussion leaves open the possibility of later, selective exceptions. The material supplied does not set a timetable or process for considering those exceptions.
“No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.”
— QEP 428, merged proposal
Enforcement and Exceptions Remain Open
The policy text names possible sanctions but the available material does not specify how suspected AI use will be detected, what review or appeal process contributors can expect, or how sanctions will be decided. It also does not define every workflow that counts as AI- or agent-assisted, beyond the broad language in the proposal.
Potential exceptions are discussed as a future possibility, not as an adopted carve-out. The proposal does not give a schedule for reviewing the ban or say whether autocomplete tools, translation systems or other specific uses will eventually be permitted. Dawson’s account of a lost contributor and the earlier policy’s poor implementation comes from the discussion; the supplied record does not provide independent detail about either.
How QGIS Applies the Moratorium
The immediate next step is implementation of the merged policy in contributions to qgis/qgis. Contributors and maintainers will need to follow the new restriction while its practical application becomes clearer. The project has not announced, in the supplied material, a separate enforcement guide, review date or process for granting exceptions.
Any later change would require QGIS to clarify which forms of AI assistance, if any, it will permit and how those uses should be disclosed or reviewed. For now, the adopted proposal provides the governing rule: AI-, LLM- and agent-assisted code contributions are not allowed in the repository.
Key Questions
What did QGIS decide?
QGIS merged QEP 428, which prohibits AI-, LLM- and agent-assisted code contributions to the qgis/qgis repository.
When was the proposal merged?
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 can happen if a contribution used AI assistance?
The proposal says the project may revert the code and sanction contributor rights if it later discovers prohibited AI, LLM or agent assistance. The supplied material does not explain how such cases will be investigated or sanctions decided.
Is any AI use allowed under the new policy?
The adopted text bars AI-assisted code contributions in the named repository. Dawson discussed possible future exceptions, such as autocomplete-like assistance or translations, but those examples are not established exceptions in the merged policy.
What policy did QEP 428 replace?
It replaced QEP-408, which allowed AI assistance subject to human review and disclosure, including an “Assisted-by” trailer for contributions.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
