Godot will no longer accept AI-authored code contributions

Original Article ↗ Hacker News Discussion ↗

Godot, a popular open-source game engine, is moving to ban AI-authored code and text contributions, arguing that AI-generated pull requests overwhelm maintainers with low-quality, verbose changes and undermine the mentoring pipeline for future human maintainers. Supporters say this policy is a pragmatic defense against “slop” PRs, legal uncertainty around training data, and the burnout of volunteer reviewers whose time is already scarce. Critics counter that the rule is blunt, hard to enforce, and risks excluding high-quality, AI-assisted work just as coding tools are rapidly improving, with some predicting forks that embrace AI as a competitive alternative.

Rationale for the no‑AI policy

  • Many see the policy as a response to “AI slop”: large, low‑effort PRs that overwhelm maintainers.
  • Goals cited: preserve reviewer time, keep code understandable by humans, avoid being downstream of unvetted AI work, and ensure contributors can maintain what they add.
  • Legal/provenance worries appear: models likely trained on GPL or proprietary code; maintainers don’t want “AI‑laundered” liability in complex codebases.

Concerns about code quality and review load

  • Reviewers report AI PRs as verbose, unfocused, and often subtly wrong while looking plausible, making review much more expensive.
  • Brandolini’s law is invoked: it’s far cheaper to generate than to refute; AI multiplies this asymmetry.
  • People liken AI PR floods to a denial‑of‑service attack on maintainers’ limited free time.

Authorship, mentoring, and community goals

  • PRs are described as social artifacts: a way to teach contributors, identify future maintainers, and build shared understanding.
  • If feedback is absorbed by an LLM rather than a growing human contributor, reviewers feel their mentoring effort is wasted.
  • Some argue authorship therefore matters even when code “works”.

Enforcement and practicality

  • Detection is expected to be heuristic and social, not technical: large, unfocused changes, AI‑style prose, unknown contributors, etc.
  • Policy primarily gives maintainers explicit grounds to close suspected AI PRs quickly and deflect debates about fairness.
  • Critics note this can misclassify genuine human work and will not stop careful AI users who review and “humanize” output.

Proposed alternatives and process changes

  • Suggestions include:
    • Strict limits on PR size, number of open PRs, and description length.
    • Requiring issues/discussion before large PRs.
    • Better tests, static analysis, and tooling; possibly AI‑assisted triage and review.
    • Separate “AI‑friendly” forks/sandboxes from which maintainers can cherry‑pick good changes.

Broader views on AI coding

  • Supporters of AI describe real productivity gains for well‑scoped tasks (refactors, ports, docs), especially when every line is reviewed.
  • Others report “vibecoding” hangovers: rapid progress followed by discovering messy, inconsistent, hard‑to‑maintain code.
  • There is disagreement over whether current models are on the verge of surpassing humans for complex systems, or are overhyped and structurally unreliable.

Implications for open source and Godot

  • Some predict AI‑embracing competitors will outpace conservative projects; others think AI‑heavy projects will degrade while Godot’s quality stance becomes an advantage.
  • Several note that open‑source contributions are increasingly driven by CV‑padding, bounties, and university assignments, with AI amplifying low‑investment participation and thus the need for stricter gatekeeping.