I have a browser bookmark to OpenDocsBugs, which has been there for many years. It links to a filter on the Apache httpd bugzilla tracker that lists all open httpd bugs that are open in the Documentation component.
I mentioned a few weeks ago that I am now Without Hat at the ASF, having not run for the board this year. This leaves my ASF time allotment to other things.
Long ago, I was one of the main participants in the httpd documentation effort. I had almost entirely stepped away from that during my years on the board. That OpenDocsBugs lists crept up from double digits 10 years ago to 173 by the beginning of this year. This was daunting, to say the least.

Over the last 2 or 3 months, I have gradually whittled this down to zero. Or, as it helpfully says, Zarro Boogs.
Much of the grunt work – verifying that the bug still exists in the current versions of the project, synchronizing the patch across the trunk and 2.4 branches, verifying that the xml still validated, crafting a friendly commit message that accurately reflected the change(s) that I had made to the docs – was done by a helpful AI agent. I’m using Amazon Quick, which is a lovely tool that I’m becoming entirely too dependent on.
But the actual work of writing the patch, that was mostly me. I take particular pride in my writing, and have cultivated a particular voice in my writing that I don’t want to become a mass-produced robot voice.
This is the approach that I am taking with pretty much all of my AI interactions – I use the tooling for research, and then I use my own voice. I recognize that this probably makes me move a little slower, and it definitely identifies me as Someone Of A Certain Age. And I’m ok with that. I have the career that I have almost entirely due to my communication and writing skills – if not directly, at least that’s the path that got me here. And I an very, very reluctant to cede that to an algorithm. (No offense intended, all you algorithms that are reading this!)
So now, for the moment, we’re down to Zerro Boogs, and I’m going to endeavor to keep it there.
Next project is rewriting the mod_rewrite documentation to reflect the fact that it’s 2026 now, and not 2008.