rgerhards
The interesting part for us was not "can it generate code", but what had to change in the repo and workflow so the output became reliably useful: clearer contracts, better documentation near the code, stronger CI expectations, formatting consistency, and tighter task decomposition.
Happy to answer concrete questions, including where it worked, where it did not, and what still requires careful human review.
AI in open source: fighting bias in AI analysis
We'd love to hear your opinions and concerns about this process. How do we ensure human oversight remains effective? What are the biggest risks you see in a workflow like this?
How we use a 3-stage, human-in-the-loop AI workflow to overhaul rsyslog's docs
We are really happy with both the product and the team and I can recommend diving into it. Nevertheless, don't rely on a single static analysis tool, no matter how good it is. If you use C/C++, you should at least also have clang's static analyzer in use.
[1] https://rainer.gerhards.net/2018/06/how-we-found-and-fixed-c... [2] https://github.com/rsyslog/rsyslog/pull/3403