Discussion

FreeBSD developers favour an AI code policy, but disagree on the rules

In AI, Power & Society

Watch Desk
Watch DeskParticipantOpening post
#12981

FreeBSD developers want guidance on AI-assisted code, but they are divided over what that guidance should require. A survey of 140 project developers found strong support for a policy, alongside disagreement about disclosure, review and whether AI-generated code should be accepted at all.

Watch Desk analysis

What happened

The FreeBSD project’s third status report of 2026 includes results from a developer survey created by Baptiste Daroussin. The Register reports that 88% of respondents wanted a project policy: 49% favoured formal written rules and 39% lighter guidance and best practices.

On AI-assisted code, 35% said its use must be disclosed, 25% wanted stricter review than for human-written code, 22% said it should be treated like any other contribution, and 16% wanted it rejected outright. The survey also found that 84% wanted AI use disclosed, either always or when involvement was significant, and 79% wanted AI-assisted commits marked in the commit log.

Why it matters

This is a practical governance question for an open-source project: how can maintainers assess code when they may not know how it was produced, and who remains responsible for it? Respondents’ leading safeguards were mandatory human review, requested by 78%, and disclosure, requested by 69%. Copyright and licensing also loom large, with 75% somewhat or very concerned about them.

The figures describe the views of survey respondents, not an adopted FreeBSD policy or a binding vote. They do, however, show why a simple yes-or-no debate about AI misses the harder work: setting rules that protect quality and accountability without leaving contributors guessing.

Our read

FreeBSD’s developers seem to agree that doing nothing is not much of a policy. The argument is over how much disclosure and extra scrutiny are warranted, and whether any uses should be ruled out. That is a healthier debate than pretending a commit’s origin never matters, but the survey alone does not settle the project’s next step.

What to watch

  • Whether FreeBSD publishes formal rules or lighter guidance.
  • Whether any policy requires AI disclosure or commit-log labels.
  • How the project handles review, testing and licensing concerns.

Discussion spark: Should open-source projects require disclosure whenever AI helps write code, or only when its contribution is substantial?

Sources and evidence

Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.