Hi Nicola,

Thanks a lot for your message and for your long experience with Hobbit and Xymon.

It’s great to hear you’d like to help and have ideas. For now, I’m focusing on getting the Git migration settled and agreed on by everyone. Broader topics like 4.4, Docker, or integrations probably make more sense to discuss once that’s clear.

By the way, I’ve invited you to collaborate on the repository. Thanks again for the feedback. Bruno

Le 14.01.2026 à 06:11, Nicola a écrit :

Hi. I have neen using Hobbit and then Xymon since about 22 years, I know shell and I know Python very well. I jave ideas on what could be added or improved, and I would love to see Xymon thrive o please count me in if I can help.

If Xymon 4.4 can be used as a replacement of 4.3, why not start from there? Can we include a docker version? I see an attempt by Dewey Sasser 10 years ago. Home assistant integration? Multi tenancy?

Nicola https://xymon.nicolacanepa.net

Bruno Manzoni via Xymon wrote:

...

Thanks Mark for checking and for the feedback.

Good to know everything looks fine on your side and that the tags and history came through correctly.

About switching the default branch to main: that’s a future step. For now, I’m avoiding making decisions on my own.

I fully agree that reaching consensus on the git forge is the next step. Once that’s clear, starting to collect issues and get things moving again would be awesome.

By the way, I’ve invited you to collaborate on the repo. Thanks very much for your feedback.

Bruno

Le 14.01.2026 à 00:10, Mark Felder via Xymon a écrit :

...

On 1/13/26 14:12, Bruno Manzoni via Xymon wrote:

...

Hi All,

I redid a test of an initial import of the Xymon SVN repository into Git:

https://github.com/xymon-monitoring/xymon-svn-mirror

The goal was a faithful copy, not a cleanup:

• full SVN history imported
• no commits rewritten or dropped
• no branches renamed
• no tags modified

Two helper scripts used for the migration (SVN mirroring and SVN-to-Git conversion) are included in the repository for transparency and reproducibility. A short document (GIT-MIGRATION.md) explains the methodology and the current status.

Current state:

• 4.x-master is still the default branch, matching the historical SVN layout
• a main branch was added to document the migration and related scripts; it will probably be removed later
• no decisions have been made yet (branch naming, cleanup, or future governance)

I would really appreciate if experienced contributors could take a look at this work, as I don’t feel qualified to fully assess it myself. Henrik, if you’re available to validate it, you’ve been invited to the repository with full access, as have JC, TOM, and others. Please let me know if access doesn’t work.

This looks similar to what my own effort produced. The tags are correctly backdated, all looks well. I think the only change that needs to happen is to alter the default branch to "main".

If we can find consensus on moving development to this or another git forge hosted somewhere/anywhere, I'd love to begin creating issues and MRs with the patches I've collected and created so we can get the ball rolling on a 4.3.31 release.

Mark

---

Xymon mailing list -- xymon@xymon.com

To unsubscribe send an email to xymon-leave@xymon.com

---

Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com