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, replacing its earlier rules for reviewed and disclosed AI use with a ban on AI-, LLM- or agent-assisted code contributions to the QGIS repository. The proposal says violations may lead to code reversion and contributor-rights sanctions; how the policy will be enforced in specific cases is not detailed in the material available.
The QGIS project has merged a proposal banning AI-assisted code contributions to its main repository, replacing an earlier policy that permitted AI use if contributors reviewed and disclosed it. QEP-428, authored by core contributor Nyall Dawson, was merged into the QGIS Enhancement Proposals repository on Oct. 7; it says violations may result in code being reverted and contributor rights being sanctioned.
The new policy states that LLM-, AI- or agent-assisted code contributions are not allowed in the qgis/qgis repository. It further says that if the project later discovers AI assistance was used, the contribution may be reverted and the contributor may face sanctions to their project rights. The proposal does not set out a detailed process for investigating suspected use or applying those sanctions.
QEP-428 replaces QEP-408, an earlier policy adapted from the LLVM project’s AI Tool Use Policy. That approach required contributors to review generated output, disclose AI assistance through “Assisted-by” trailers, and avoid posting unreviewed agent-generated comments. The new proposal instead sets a general prohibition, while leaving open the possibility that some uses could be permitted later through case-by-case decisions.
The proposal passed its discussion period on Oct. 5 and moved to a vote before the Oct. 7 merge. The source material identifies Dawson as the author and reports his reasoning in the pull-request discussion; the change is recorded in the QGIS Enhancement Proposals repository’s pull request #387.
A New Rule for QGIS Code
The change puts QGIS among software projects drawing a firm boundary around AI-assisted contributions. For maintainers, a blanket rule may make it easier to apply a consistent standard than a policy that depends on contributors reviewing and documenting generated output. It also means contributors must now avoid AI assistance when preparing code for the QGIS repository, unless the project later defines an exception.
The policy matters beyond the immediate code-review process because it changes the terms of participation in a widely used open-source geographic information system. Its stated possibility of reversion and contributor sanctions gives the rule consequences, although the proposal does not explain how those outcomes would be decided. Whether the approach improves confidence in contributions or discourages contributors remains unestablished.
As an affiliate, we earn on qualifying purchases.
From Disclosure to Prohibition
QEP-408 had taken a disclosure-and-review approach: contributors could use AI tools if they checked the output and identified assistance. The new QEP-428 proposal reverses that premise for code contributions, replacing permitted use under conditions with a prohibition in the QGIS code repository.
In the pull-request discussion, Dawson said the earlier process was not happening in practice and argued for starting with a closed door, with selective openings considered later. He named possible exceptions such as using AI as an autocomplete replacement or for translations. Dawson also said the project had already lost at least one highly valued contributor because of the earlier policy. That account is Dawson’s statement; the supplied material does not identify the contributor or independently substantiate the claim.
“No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.”
— QEP-428, merged proposal
As an affiliate, we earn on qualifying purchases.
Enforcement and Exceptions Remain Open
The proposal names possible consequences, but the available text does not specify how AI use will be established, who will decide whether a contribution breaches the rule, or what process contributors can use to challenge a decision. It is also unclear whether sanctions will follow a defined scale or be decided individually.
Dawson discussed potential exceptions, but the merged proposal described in the source material does not establish a list of permitted uses. The precise treatment of tools such as autocomplete, translation systems, and other forms of assistance therefore remains unsettled in the available record. The claim that the former policy cost the project a valued contributor is attributed to Dawson and is not independently verified here.
geographic information system software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Watch for Policy Guidance
The next practical development to watch for is whether QGIS maintainers publish guidance explaining how the ban applies to specific tools and how the stated sanctions would work. Dawson’s comments indicate that case-by-case exceptions may be considered, but no timetable or approval mechanism is given in the source material.
Until the project clarifies those points, contributors considering code changes should follow the rule as written: AI-assisted code contributions are not permitted in the named repository. Any future revision, exception, or enforcement guidance would clarify how the policy operates in practice.
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.
When was the proposal merged?
The proposal passed its discussion period on Oct. 5 and was merged on Oct. 7, 2026, according to the QGIS Enhancement Proposals pull request.
What happened to the previous AI policy?
QEP-428 replaces an earlier policy that allowed AI use if contributors reviewed the output and disclosed assistance. The new policy sets a general ban on AI-assisted code contributions.
What penalties does the proposal describe?
The proposal says code may be reverted and contributor rights may be sanctioned if AI assistance is discovered. It does not detail an investigation or appeals process in the material available.
Are any AI uses exempt?
Dawson discussed possible later exceptions, including autocomplete-style assistance and translations, but the source material does not establish formal exemptions or a process for requesting them.
Source: hn
Columbus Day / Indigenous Peoples' Day Picks
long weekend sales
As an affiliate, we earn on qualifying purchases.
