QGIS enacts moratorium on AI contributions

Scope and Rationale of the QGIS AI Moratorium

• Policy bans “LLM/AI/agent-assisted” contributions to QGIS core (not the whole geospatial ecosystem).
• Maintainers say motivation is practical, not ideological: overwhelmed by low‑quality, AI‑generated PRs and issues.
• Prior policy allowed “human in the loop”; maintainers now feel that was insufficient.
• Some note this is framed internally as a temporary moratorium until better processes exist.

Workload, “Slop”, and Maintainer Bottlenecks

• Maintainers report large, verbose PRs with weak understanding from contributors, often clearly LLM-driven.
• Reviewing such PRs is costlier than fixing the issue themselves with their own AI tools.
• Similar experiences are reported by other OSS projects: many trivial or edge‑case bug reports, long AI-written descriptions, and duplicated or hallucinated issues.

Definition, Enforcement, and Trust

• Several commenters criticize the policy’s vagueness: what counts as “AI-assisted”?
• Others argue strict legalistic definitions aren’t needed; it’s a trust-based rule to justify rejecting suspicious PRs.
• Some worry about “witch hunts” and inconsistent enforcement; others counter that perfect detection isn’t required for the policy to be useful.

Implications for Open Source, Forks, and Contributions

• Some predict this accelerates the decline of “open contributions”; maintainers will increasingly do all coding (possibly with AI) and accept fewer external PRs.
• Others say contributors can always fork and use AI as they like; the market and community will decide which forks matter.
• There’s concern about how new maintainers will emerge if entry paths via PRs shrink.

Code Quality, Safety, and the GIS Domain

• GIS and QGIS are described as safety- and accuracy‑critical, often used in infrastructure, urban planning, and scientific research.
• Commenters argue subtle, domain-specific bugs can have serious consequences; LLMs are seen as especially brittle around geospatial math and coordinate systems.
• Some point out QGIS already has complex, imperfect human‑written code; banning AI doesn’t magically guarantee quality.

AI Usefulness vs. Risks and Perception on HN

• Many report large personal productivity gains from LLMs (bug finding, typing, tests, tedious refactors).
• Others cite studies and experience where AI coding slows work or produces hard‑to‑maintain “house of cards” systems.
• A recurring theme: the bottleneck is no longer “writing code” but understanding, reviewing, and staying aligned with it—AI makes that harder by inflating volume.
• Meta‑discussion notes polarized attitudes on HN, accusations of astroturfing, and fears about job loss vs. claims that AI is just another tool.

Alternative Policy Ideas

• Suggested alternatives:
  • only allow AI for trusted contributors,
  • proof-of-humanity via small payments or higher entry hurdles,
  • explicit “AGENTS.md” standards for AI‑assisted PRs,
  • using AI to triage or review PRs rather than generate them.
• Linux kernel’s stance (AI allowed but submitter fully responsible) is cited as a more nuanced model, though that community also rejects low‑effort AI fixes aggressively.