hi, security team, I keep getting fishing emails.

security team: you mean phishing?

no. fishing. I'm pretty certain.

Mesa is working to update our contributor guide. Can you guess why?

Did you guess AI?

Because if you did, you'd be right. I don't want to put anyone on blast here so please don't go digging to find the motivating MR and harass the contributor or anything like that.

But the situation was exactly what you might think. Someone ran ChatGPT on the code and asked it for suggestions on making it more performant. They applied a bunch of the changes against their local branch, tested it, and found that it gave maybe a 0.5-1.0% perf boost in some titles.

That's totally fine. I don't care what tools you use to find a bottleneck. I'll happily take more FPS, no matter who found the issue or how. If some AI assistant helps you find things no one else has found and lets us make drivers faster, great!

But that's not what happened.

What happened next is that they then tried to make it the Mesa project maintainers' job to sort through the shit ChatGPT spit out and decide what's useful and what's not and why the changes helped and whether or not they were correct. The contributor had no no idea and, more importantly, they had no desire to actually learn about the Mesa code-base or the hardware in question. They just wanted to run ChatGPT and send its suggestions towards upstream.

This is not useful. This is not contributing. It's just burning maintainer time sorting through AI hallucinations. We have enough mediocre code to review that comes from actual humans who are actually trying to learn about Mesa and help out. We don't need to add AI shit to the merge request pile. If you don't understand the patch well enough to be able to describe what it does and why it makes things faster, don't submit it.

So now we're making it really clear: If you submit the merge request, you're responsible for the code change as if you typed it yourself. You don't get to claim ignorance and "because the AI said so". It's your responsibility to do due diligence to make sure it's correct and to accurately describe the change in the commit message.

Some things shouldn't have to be explicitly written down but here we are... 😩

> 1989: NeXTSTEP was built upon Mach and BSD, initially 4.3BSD-Tahoe
> BSD Tahoe
> 2025: macOS Tahoe

...

Now its interesting!

#apple #macOS #bsd #unix

Hello everyone.

I've been a BSD user for a long time, even back to the early 2000s when I ran FreeBSD instead of Linux on my Abit BP6.

That was the era I also using NetBSD and OpenBSD on a variety of hardware, some of which I still have.
E.g. a VaxStation, SUN IPX, PA-RISC HP 9000, etc.

In the last year or so I've had FreeBSD with sway on a laptop.

A tale as old as schools with computers and kids lol.

The Information Commissioner's Office apparently just found out what kids do with computers.

Ah the memories come flooding back.

https://www.bbc.com/news/articles/c203pedz58go