Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

AI Usage Policy

This policy covers code, documentation, pull requests, issues, comments, and any other contributions to the Servo project. These contributions must not include content generated by large language models, with the exception of minimized test cases.

Reasoning

For now, we’re taking a cautious approach to these tools due to their effects — both unknown and observed — on project health and maintenance burden. This field is evolving quickly, so we are open to revising this policy at a later date, given proposals for particular tools that mitigate these effects. Our rationale is as follows:

Maintainer burden: Reviewers depend on contributors to write and test their code before submitting it. We have found that these tools make it easy to generate large amounts of plausible-looking code that the contributor does not understand, is often untested, and does not function properly. This is a drain on the (already limited) time and energy of our reviewers.

Correctness and security: Even when code generated by AI tools does seem to function, there is no guarantee that it is correct, and no indication of what security implications it may have. A web browser engine is built to run in hostile execution environments, so all code must take into account potential security issues. Contributors play a large role in considering these issues when creating contributions, something that we cannot trust an AI tool to do.

Copyright issues: Publicly available models are trained on copyrighted content, both accidentally and intentionally, and their output often includes that content verbatim. Since the legality of this is uncertain, these contributions may violate the licenses of copyrighted works.

Ethical issues: AI tools require an unreasonable amount of energy and water to build and operate, their models are built with heavily exploited workers in unacceptable working conditions, and they are being used to undermine labor and justify layoffs. These are harms that we do not want to perpetuate, even if only indirectly.

Not Allowed

  • Submitting issues text, pull requests, comments, or communication generated by AI tools.
  • Submitting pull request descriptions generated by AI tools. Please follow project best practices when writing pull request descriptions.

Allowed

  • Literal translation of a comment you have written yourself from your native language into English.
  • Using AI tools to find bugs and security issues:
    • Issues should contain no AI-generated prose.
    • All output must be human verified before filing issues. You must not simply trust the tool’s output.
    • Minimized test cases / reproductions are allowed and encouraged, whether generated with fuzzers, large-language models, or other tools. Minimization with a tool like lithium is strongly encouraged.
  • Using AI tools to help understand Servo’s codebase:
    • Note that tools can sometimes be wrong or misleading, so it is important to be critical with the tool output and to double-check everything.
    • Consider asking your questions on Zulip instead.
  • Using AI tools to review a pull request:
    • This must be done privately. No AI review or prose should be posted.
    • Verify all claims in the review, as it is not uncommon that the tools are incorrect.
    • Be aware of the limitations of a single change and identify what should be saved for followup work. Explain known issues in the pull request description and your plan for fixing them.

The Servo maintainers reserve the right to close or delete any issue, pull request, and comment that does not meet the standards of this policy. Generated code, apart from minimized reproductions, are strictly prohibited, but the Servo maintainers may ask you to rewrite prose that is not allowed by this policy.