Xymon development inquiry

Hi Tom, 
I did Invite you to xymon-monitoing repo!
Bruno

I have contributed to and used Xymon for decades since the Big Brother days. My team used it to monitor hundreds of systems at my former workplace. I have now been retired for 6 years and use Xymon at home to monitor my local network.  I have been running the 4.4.0 alpha1 release on Rocky Linux 8 and 9 platforms and have submitted many patches for it.  I have created several external monitors for my local home devices, such as ASUS routers, HP and Epson printers, SolarEdge inverter, and Foscam IP cameras.

I am willing to help in any way I can, but I have no experience running repositories.  I do have a good background in C and Linux. I agree that it would be best if a single source for the repository would be best.

Tom Schmidt

On Tue, Jan 13, 2026 at 7:36 AM Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:

Thanks Copilot.

Let's refrain from AI slop in this mailing list, please.

On Tue, Jan 13, 2026 at 9:24 AM Bruno Manzoni via Xymon <xymon@xymon.com> wrote:

HI all

Instruction / call for feedback

This summary was prepared from mailing list discussions and user input to give a clear overview of the current Xymon situation.

Feedback from users, maintainers, and operators is strongly requested to confirm this view and to indicate their willingness to help by briefly listing their relevant skills, availability, and areas of interest (e.g. maintenance, releases, packaging, testing, or specific technical domains).

Resume

- Xymon development is largely inactive upstream.
- Version 4.3 is the only production-ready release.
- Version 4.4 is unfinished and experimental.
- Most maintenance work is done downstream, causing duplicated effort.

Main problem

- There is no active upstream maintainer group and no modern collaboration workflow.
- This is the root cause of fragmented patches, stalled releases, and unfinished work (notably IPv6 in 4.4).

Minimal requirements / immediate next steps

- One public Git repository accepted as the upstream reference.
- One or two interim maintainers with merge and release responsibility.
- One maintained production branch: 4.3.
- A basic issue list to track bugs and patches.
- A first consolidated 4.3.x maintenance release.

Who can help

- Distribution maintainers (Debian, FreeBSD).
- The original author (Henrik) for CVS migration support.
- Production users for testing and validation.
- Community members willing to help maintain releases.

Bruno

Le 13.01.2026 à 10:13, Henrik Størner via Xymon a écrit :

Hi,

speaking for myself, I must admit that I haven't worked on Xymon for several years. Just lurking on the mailing list occasionally.

J.C.Cleaver was maintaining the 4.3.30 version and I was working on the 4.4 branch, but both efforts have stalled - mine certainly has.

A Git repo would undoubtedly make it easier for people to contribute than the current Sourceforge CVS repository, so if the is an interest in maintaining or even developing Xymon further, then that would be a very good first step.

About the state of the various branches, 4.3 is certainly the production version - this should be priority #1 when moving to Git. The 4.4 branch is - as Roland mentions - very unfinished and alpha-like. It was an attempt on my part to move all of the networking code into a library with support for both IPv4 and IPv6 - quite a bit of it was working, but it was not completed or even stress-tested. It is certainly not bug-free.

I cannot offer to restart Xymon development by myself, but I will be happy to assist anyone with getting the code moved from Sourceforge to a Git repo - if you need any special access to Sourceforge.

Regards,
Henrik

Roland Rosenfeld skrev den 13-01-2026 08:47: