has freebsd taken a stance on ai? at a glance i'm not seeing references to systemd in their documentation pages

#FreeBSD #NoAI

Contributions to FreeBSD: LLMs and AI

From <https://github.com/freebsd/freebsd-src/blob/main/CONTRIBUTING.md#when-not-to-use-a-pull-request> for the src tree:

"Do not submit a pull request for … changes generated by AI tools without substantial human review and validation."

Comparable lines from a July 2025 edition:

<https://github.com/freebsd/freebsd-src/blob/015ae668899383ebf7969863dae1b45e169bbcdc/CONTRIBUTING.md?plain=1#L53-L54>

Back to June 2025, the Core Team Update at the FreeBSD Developer Summit, <https://www.reddit.com/r/freebsd/comments/1mpelrz/comment/nk0m7bg/> includes links to:

― part of the recording

― <https://reviews.freebsd.org/D50650> @dch – ⚙ D50650 committers: add AI policy.

The more recent review – accepted:

⚙ D54817 Committer's Guide: Add project's AI policy and link to AI guide

<https://reviews.freebsd.org/D54817>

Related:

<https://www.freebsd.org/projects/summerofcode/#llm>

@krishean

#FreeBSD #GSoC #LLM #human #validation #AI

freebsd-src/CONTRIBUTING.md at main · freebsd/freebsd-src

The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests.... - freebsd/freebsd-src

GitHub
@grahamperrin @dch @krishean has this been resolved in a consistent way? I see two open diffs (D50650 and D54817) that have different language. There’s also a comment in one (https://reviews.freebsd.org/D50650#1253032) that mentions another diff that no longer seems to be public. Personally I prefer the language in D50650 and I’m concerned that the language in D54817 (“Consider licensing and the AI service terms, including any attribution requirements.”) allows too much wiggle room for people to contribute code for which they can’t be 100% certain of provenance and/or ownership. Effectively: “LOL I considered it and decided I didn’t care.”
⚙ D50650 committers: add AI policy

@fedward

Approved D54817 <https://reviews.freebsd.org/D54817> for [[ai-policy]] in the Committer's Guide describes ai-guide as a supplement.

D54366 <https://reviews.freebsd.org/D54366> for the ai-guide surprises me, I didn't realise that it's not visible to the public.

@dch @krishean

⚙ D54817 Committer's Guide: Add project's AI policy and link to AI guide

@grahamperrin @dch @krishean I created an account so I can read D54366 and … I hate it. I don't think it places enough guardrails, and it's also way too long. In light of the fact that legal ownership of AI generated code is still in doubt, and in light of the fact that Linux is maybe on the wrong side of the AI line already (at least considering the kernel and systemd), I believe a stronger "just don't use it until the legal framework is more firmly established" stance is called for. I'm sensitive to the style and/or bug finding arguments, but I believe FreeBSD is in a position to become a safe harbor for people fleeing Linux for AI reasons, and I fear that policy as written doesn't provide enough reassurance.
@fedward that would be my personal position too but we have to find consensus, if possible @grahamperrin @krishean
@dch @grahamperrin @krishean I mean, this is probably the wrong forum for me to be protesting in, and I'm Just One Guy™, but townspeople don't tend to come out well in stories where they compromise with the people who want to poison the well. "It's only a little bit of poison," they say.

@fedward @dch @grahamperrin i am reminded of a recent post/thread* likening it to brain poison

* https://mastodon.social/@glyph/116220491984902015

@krishean @fedward more than that, I'm reminded of the discussions in June 2025.
@grahamperrin @dch @krishean alright, I just commented on D54366, which is a hell of a first contribution to anything.

@fedward

"… As my boss in my non-coding job says, people don't read. …"

Too true, for too many readers.

<https://people.freebsd.org/~grahamperrin/style/writing/tips/>

– and then click the word "concise" for a ninety-nine page primer (PDF, A4). That's ninety-one pages longer than a long primer should be.

A good primer should be no longer than four pages – visualise an A3 sheet, duplex, folded – with directions.

Eight pages, max.

Off with my head, et cetera.

#FreeBSD #documentation