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 banning AI-, LLM- and agent-assisted code contributions to the qgis/qgis repository on Oct. 7. The policy says discovered use can lead to code reversion and contributor-rights sanctions; the project’s stated approach is to begin with a ban and consider limited exceptions later.
The QGIS project has merged a proposal banning AI-assisted code contributions to its main software repository, replacing an earlier policy that allowed AI tools under human review and disclosure rules. The change, set out in QEP-428 and merged on Oct. 7, says contributions found to have used AI, large language models or agent-based workflows may be reverted and the contributor’s rights sanctioned.
The proposal, titled “No AI contributions permitted,” was submitted by QGIS core contributor Nyall Dawson in pull request 387 to the QGIS Enhancement Proposals repository. The pull request records that the proposal passed its discussion period on Oct. 5, moved to a vote and was merged into the repository’s main branch two days later.
QEP-428 says: “No LLM, AI or agent assisted code contributions are allowed in the qgis/qgis repository.” It adds that if the project later discovers AI assistance was used, the contribution may face code reversion and the contributor may face sanctions to their project rights. The text does not describe the new rule as limited to code produced entirely by AI; it covers contributions made with AI or agent-based assistance.
The merged proposal replaces QEP-408, an earlier policy adapted from LLVM guidance. That approach called for contributors to review AI-generated output, disclose assistance using “Assisted-by” trailers and avoid unreviewed comments from AI agents. Dawson argued in the discussion that the earlier process was not being followed in practice.
A New Rule for QGIS Contributions
The decision changes the conditions for contributing code to QGIS, a widely used open-source geographic information system. Contributors who used AI assistance now face a stated risk of having work reverted and project rights sanctioned if that use is discovered. The wording also gives maintainers a direct basis to reject affected contributions rather than rely on disclosures and review.
For open-source projects weighing AI tools, QGIS offers a clear example of a stricter governance choice: prohibit assistance for now instead of relying on contributors to disclose it and reviewers to assess it. That approach may reduce uncertainty about whether AI-assisted code meets the project’s standards, while also limiting tools available to prospective contributors. The proposal itself does not quantify either effect.
Dawson said the project had already lost at least one “extremely high value” contributor as a result of the previous policy, but that is his account in the pull-request discussion, not an independently documented measure of the policy’s impact. The project’s decision matters both to QGIS contributors and to other maintainers watching how communities set rules for AI-generated or AI-assisted work.
As an affiliate, we earn on qualifying purchases.
From Review Rules to a Ban
QEP-408 took a human-in-the-loop approach: AI tools could be used, but output was to be reviewed and disclosed. It also barred unreviewed agent comments. QEP-428 says the safeguards did not work as intended in practice and replaces that framework with a prohibition on AI-, LLM- and agent-assisted code contributions to the specified repository.
In the pull-request discussion, Dawson said the intention was to start with a closed door and potentially open it selectively later. He gave autocomplete-style assistance and translations as possible areas for future exceptions. Those examples describe possible later changes; they are not exceptions established by the merged text.
The proposal was merged into the QGIS Enhancement Proposals repository, which records project policy proposals. Its text specifically names the qgis/qgis repository as the place where AI-assisted code contributions are not allowed. The source material does not establish a broader prohibition covering every QGIS-related project or all uses of AI by the community.
““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.
Scope and Enforcement Questions
The merged text does not spell out how the project will determine whether AI assistance was used, what process contributors can follow to challenge a finding, or how sanctions to contributor rights would be applied. It also does not detail whether different tools or forms of assistance will be treated differently.
Possible exemptions for autocomplete-like uses or translations were mentioned by Dawson in discussion, but the proposal does not define or adopt them. It remains unclear whether maintainers will propose separate rules for those cases, and whether the policy will be revised after experience with the ban.
The available source confirms the proposal’s merge and its wording, but does not provide later enforcement cases or a separate announcement explaining implementation. The reported loss of a valuable contributor is Dawson’s claim; the source material does not name that person or provide further evidence of the circumstances.
As an affiliate, we earn on qualifying purchases.
Possible Exceptions May Follow
The immediate next step is for QGIS maintainers and contributors to work under the merged QEP-428 rule for code contributions to qgis/qgis. The proposal sets out consequences but does not provide a rollout schedule, a transition period or a published enforcement procedure.
Dawson’s discussion comments point to a possible later review of specific cases, including autocomplete-style tools and translations. Any such opening would require further project action; the current merged policy does not itself authorize those uses. Whether QGIS publishes clarifications, establishes an appeal process or amends the rule remains to be seen.
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 decide?
QGIS merged QEP-428, which prohibits AI-, LLM- and agent-assisted code contributions to the qgis/qgis repository.
When was the proposal merged?
The pull request records that QEP-428 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 discovered AI assistance may result in code reversion and contributor-rights sanctions. It does not specify a detailed enforcement or appeal procedure.
Are autocomplete tools or translations exempt?
Not under the merged text. Dawson mentioned those as possible areas for future case-by-case exceptions, but QEP-428 does not establish them.
How does this differ from the previous policy?
The earlier QEP-408 policy allowed AI use subject to human review and disclosure. QEP-428 replaces that approach with a ban on AI-assisted code contributions to the named repository.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
