@grahamperrin @dch @ltning I am not trying to "fan flames" so to speak, but perhaps I did overstate.
It HOWEVER does seems accurate to say things have drifted quite a bit from what was discussed at the last BSD Core Team update https://youtu.be/tUmeRqzczhA?si=5X5F8y-3wx28__9W
https://github.com/freebsd/freebsd-src/commit/6495dafd58b94a44fc9bc966ef47d6bc6916f5b9
AND I do feel like I should be allowed to express my disappointment at such events, while not being accused of causing an unnecessary panic.
LLM code IS being accepted today.

@grahamperrin @dch @ltning I have been telling folks here in mastodon and in real life, for months about #FreeBSD's draft policy against LLM code contribution. I resumed using FreeBSD after having spent years away, due in large part to positive indicators like that.
AND in the past couple days multiple FreeBSD committers have alternatively told me "no decision has been made" or discussed at length in replies of how soon LLM in code reviews by some members will be done, and describing generative AI in floss as an arms race that FreeBSD cannot afford to loose out in.
FreeBSD has already made one popular list of FLOSS software accepting LLM code. (Rightly or wrongly).
I am frustrated that there is no clear communication on this point to the "people in the pews" who are concerned about this; and a little tired of feeling like people are telling me I am wrong for expressing my disappointment, in the midst of this chaos.
Users are trying to figure out how to keep their software stack slop free today.
@grahamperrin Chaos being short for:
A lack of clear public messaging, and different freebsd committers seemingly telegraphing very different realities on the ground.
that's not chaotic.
Agree to disagree. It certainly feels that way with all the folks replying to me lately.
AND again thanks for telling me how to feel about this.
@trashheap @grahamperrin I don't know about #FreeBSD but #NetBSD has policy of not accepting AI/LLM generated code