Xymon Mailing List Archive search

Thoughts on the new Xymon organization - feedback appreciated

list Josh Luthman
Sat, 30 May 2026 10:57:47 -0400
Message-Id: <CAN9qwJ8+fDK8vX=user-2f3401f74879@xymon.invalid>

On the initial post...
>- documentation is still fragmented between SourceForge, mailing lists, distro patches, wiki pages, and GitHub discussions,

Is there anything that's on SF/patches/wiki pages that is NOT on the Github pages at this point?  I am happy to help copy/paste/format to keep documents all in one place.

On Sat, May 30, 2026 at 6:18 AM Bruno Manzoni <user-81df5df13c04@xymon.invalid> wrote:

Hi Josh, 
There's already a first take on this in the xymon-problems repo. 
See the documentation issue: https://github.com/xymon-monitoring/xymon-problems/issues/8

It's not new work: most of it was written back in 2023 and extracted from the mailing-list discussions
I've just added a few things I came across since. So it may well be inaccurate or out of date. 
So treat it as a starting point, not a final answer.

Have a look and see what you think and if it answers some of your questions. 
Happy to help with any other questions (if I am able to), and if you'd like to change or add anything: I'll gladly help make it happen !

Bruno

Le 29.05.2026 à 17:36, Josh Luthman a écrit :
Where do we want all of the documentation to end up?

On Thu, May 28, 2026 at 8:26 AM Ralph M <user-00a5e44c48c0@xymon.invalid> wrote:
Were you thinking of deadcat.net for plugins and things??  I don't know what happened to that, but there's another site called xymonton:


Ralph Mitchell



On Thu, May 28, 2026, 8:12 AM Nicola <user-2c63804b6921@xymon.invalid> wrote:
My 2c on the next steps.
I think we should move the IPv6 changes to a further version (5.0?) while using 4.4 as the "dropping compatibility" release to modernize the codebase and ease the maintenance.
In the 4.4.x we could incorporate the encrypted/authenticated communication, which I think is a less impacting change.
Reviving something like sleepycat (if I remember correctly the name), or a repo of useful plugins for particular monitoring types could be useful.

Sorry for being not much active recently (life and work impacted my available time)

Nicola


Il giorno gio 28 mag 2026 alle ore 08:56 Bruno Manzoni via Xymon <xymon@xymon.com> ha scritto:
Hi all,

First of all, many thanks to everyone involved in the new Xymon organization and the recent work around the project. A lot of effort has clearly gone into modernizing and stabilizing the codebase while still preserving the spirit and simplicity of Xymon.

1. The new governance model is a very positive step for the project:


The fact that at least two people are now involved in validating and merging changes gives much more legitimacy and long-term stability to the project. It certainly slows things down a bit, but for infrastructure software this is probably the correct tradeoff. It reduces the risk of unilateral decisions and helps keep the technical direction coherent.

2. The modernization effort is also going in the right direction.

One major goal of the new organization is bringing Xymon back to a stable and maintainable upstream state, while progressively reintegrating improvements that historically existed only in downstream FreeBSD and Debian repositories (and some in the 4.4 alpha branch).

The work achieved so far in this direction is very encouraging. Several important steps have already been achieved:
- GitHub Actions now automatically builds and validates Xymon across multiple platforms,
- many Linux, FreeBSD, NetBSD, and pkgsrc portability and build issues were fixed upstream,
- parser cleanup and hardening improved robustness,
- several memory leaks and stability issues were corrected.