As others have said, I'm keen to help where I can, although I'm not an accomplished C programmer, and really don't have any skills in software development.

Moving the source code repository seems a fairly obvious way to modernise the workflow. I'm totally behind this.

There are two ways I interact with the current Xymon codebase. One is via the source code, and the other is to install packages from the official repository aka Terabithia. This second touch point is important in a corporate environment that has a deployment model that relies on reliable and trusted repositories, and requires long-term consistency. I'd be hesitant to switch repositories from Terabithia to something new, until I became confident it would still be around in 18 months.

To a non-insignificant degree, Terabithia is part of the current Xymon ecosystem (for me). It would be ideal for new releases to be packaged up and then published on the existing Terabithia repo. It's not clear how this would happen. If JC is able to continue to maintain Terabithia, hosting the building and publishing process, pointing instead at the new source code repo, then this would be a huge benefit to the project. Alternatively, perhaps JC would prefer to hand over the domain to another volunteer, to maintain the existing repo URLs that are configured on no doubt thousands of systems.

(Of course, not wanting to diminish the importance of other package maintainers. I'm just Red Hat centric, as I imagine would be common for corporate deployments.)

This thread has been a place where people have expressed their frustrations with the current release of Xymon. I think it's helpful to do this, and I also like that people are suggesting solutions that could be implemented in new releases. This is aspirational, and I encourage this discussion. At the same time, none of the discussion will lead to any progress unless and until the basics are in place: a) source code repo, b) build and test pipeline, c) leadership team with time to vet contributions and publish releases. (And hopefully, selfishly, an RPM repository.) We should not lose focus on these objectives in the short term. And I'm heartened that we've seen so much progress in such a short time, thanks to this generous and insightful community.

Cheers
Jeremy