Libreswan's Online Documentation
View the Project on GitHub libreswan/libreswan.github.io
SupportHere are the most common reasons for something being flagged as
Slop.
We’re looking for improvements. If we wanted to turn Libreswan into A.I. generated mush, we would do it ourselves.
A.I. submitted pull-requests seem to consistently skip this step.
We’re not asking for much, but we are looking for a Human touch.
Please provide us with a brief overview of what’s happening, and especially the motivation.
A.I. likes to rationalize what was changed in excruciatingly detailed ChangeLogs that no one will read; anyone needing to know what changed will look at the diff.
We’re not asking for much, but we are looking for a Human touch.
Read a few commit messages, you’ll quickly pick up the style. The key thing is to keep it short. If there’s something complicated going on, make it a comment in the code. That way we’ll see it when we read the diff.
Like a politician, A.I. is selective with the truth.
If A.I. doesn’t know what it doesn’t know, how can we trust its analysis.
The bug reporting form has some very specific requests. Notably, a non-debug log of the entire exchange, so we can all understand the big picture and figure out the root cause.