Community¶
Users group¶
The Keepalived Users Group at Groups.io is the place to ask questions, share configurations and follow announcements. It replaces the old SourceForge mailing lists.
Subscribe to the group View the archives
Source and issues¶
Development happens on GitHub. Report bugs, propose features and read the code there:
-
Repository
The official source tree and git history.
-
Issue tracker
Search existing reports before opening a new issue, and include a minimal configuration that reproduces the problem.
Using AI tools¶
AI tools are welcome on Keepalived, yet they work best as a support for the effort and not as a replacement for it. The core team keeps the code base small, clear and auditable, so large machine generated patches and verbose content work against that goal and cost the maintainers time.
Bulk will be ignored
Large machine generated code, comments or content will simply not be read, and the core team will ignore it. Keep your work lean and to the point whether or not an AI helped you write it.
When you open an issue with the help of an AI, do not let the tool do all the work. Read and understand the problem first, then write the report so it stays clear, simple and to the point. A short and well understood report saves the core team from guessing what the tool actually meant.
When you propose a patch produced with an AI, make it simple, clear and coherent with the surrounding code, and keep it focused on the problem. Drop any large block of generated comments. A comment earns its place when it stays short and explains why the code does something, because the code already shows what it does and how.
Assisted-By
When a commit includes code that an AI helped to generate, record it with an
Assisted-By: trailer in the commit message:
Stay updated¶
Release announcements and updates are posted on the Keepalived account on X.
Historical lists¶
The original SourceForge mailing lists are no longer active. They stay online for their archives: