September 2026 - Xymon - Xymon mailman web

Nobody is watching the repository, including me
by Bruno Manzoni 20 Sep '26

20 Sep '26

Hello everyone, Being a collaborator notifies you of nothing: on GitHub, rights and notifications are unrelated. What subscribes you is the Watch button, and on xymon-monitoring/xymon nobody was using it, myself included. So when Scot opened #521, #522 and #523 last week, GitHub announced them to no one. Three clicks fix that, at the top right of https://github.com/xymon-monitoring/xymon Watch -> Custom -> Pull requests. No membership needed, the repository is public. And if you want to join the organisation, just let us know. Cheers, Bruno

5 9

xymon-rpm pull requests
by Scot Kreienkamp 18 Sep '26

18 Sep '26

Yesterday I closed the two pull requests I opened for the wrong xymon.spec file, and created two new pull requests for the xymon.spec file in the xymon-rpm repo. In short, these are the two issues: * On the client rpm install /etc/xymon-client/clientlaunch.d is not created. It should be, Debian already creates it. * On the server rpm install, it places the httpd config for xymon but doesn't signal httpd to reload configs. That scenario is a little less clear-cut as to whether it should be automatic. My opinion is that it should be. I opened pull requests for both changes. All tests have passed and they're waiting for review. Scot Kreienkamp | Principal Applications Infrastructure Architect | La-Z-Boy Incorporated (734) 384-6403 | 1-734-915-1444 | Scot.Kreienkamp(a)la-z-boy.com One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com<http://www.la-z-boy.com/> facebook.com/lazboy<http://facebook.com/lazboy> | instagram.com/lazboy<https://instagram.com/lazboy> | youtube.com/lazboy<http://youtube.com/lazboy> [cid:lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png] This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

2 1

Review rules, the backlog, and a proposal for when nobody comes
by Bruno Manzoni 17 Sep '26

17 Sep '26

Hello everyone, CONTRIBUTING.md now follows the June conversation on this list — the rules from "The Next Release Is Within Reach" on 16 June, with the condition I added the next morning after the one objection. It also says what the GitHub ruleset really enforces, and on whom. https://github.com/xymon-monitoring/xymon/blob/main/CONTRIBUTING.md It is there because nobody objected in June, not because anyone agreed — say if you disagree and I will change it. The backlog, measured: 53 ready for review (79 open, 26 of them drafts), median 20 days since being marked ready. Nothing is abandoned — none untouched for a fortnight — because I keep rebasing them. And the rate was never the problem: 60 merged between 9 August and 3 September, 51 of them with a review. Then it stopped. Nothing read or reviewed since 30 August, nothing merged since 3 September. To resolve this I propose to add a delay before bypassing a PR: - documentation, tests — 1 week (current 0 days) - build and CI — 2 weeks (current 0 days) - bug fixes — 1 month (current: never) - everything else — 2 months (current: never) The clock runs from when it was marked ready, and any review ends the wait — this is the fallback, not the path. Of the 53, 19 could go in today and the rest within two months with nobody doing anything. The cost: two months means a feature can land unread. The bigger risk runs the other way — a project where finished work cannot move is one that stops. None of it produces a reviewer or a contributor, and that is what we really need. Let me know what you think! Cheers Bruno

4 5

Snapshot feedback
by Scot Kreienkamp 17 Sep '26

17 Sep '26

Hey guys, just wanted to pass along some feedback on the snapshot release rpm install. I have the client deployed to about a dozen RHEL9 servers for testing, and I'm working on deploying a server. * On the client rpm install /etc/xymon-client/clientlaunch.d is not created. It should be, Debian already creates it. * On the server rpm install, it places the httpd config for xymon but doesn't signal httpd to reload configs. That scenario is a little less clear-cut as to whether it should be automatic. My opinion is that it should be. I opened pull requests for both changes. Scot Kreienkamp | Principal Applications Infrastructure Architect | La-Z-Boy Incorporated (734) 384-6403 | 1-734-915-1444 | Scot.Kreienkamp(a)la-z-boy.com One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com<http://www.la-z-boy.com/> facebook.com/lazboy<http://facebook.com/lazboy> | instagram.com/lazboy<https://instagram.com/lazboy> | youtube.com/lazboy<http://youtube.com/lazboy> [cid:lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png] This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

4 12

alternate "Xymon Mailing List Archive" Server
by Bruno Manzoni 17 Sep '26

17 Sep '26

Hi Guys, As Jeremy likes it, let me share some work I did (when repairing the Mailman server earlier this year): An *alternate "**Xymon Mailing List Archive"* Server https://xymon-monitoring.github.io/xymon-discussion-public/ <https://xymon-monitoring.github.io/xymon-discussion-public/> Why I didn't share it earlier: * This does not bring anything the current mailing list does not already provide. What is nice: * Searchable as a first-class feature. * Simple UI, following Xymon's one-click philosophy. * Folded past conversations for easy reading. * Anonymized. * Raw archive of the current mailing list on GitHub. * Hosted entirely on GitHub. What is not nice: * Custom-made: it probably needs more maintenance than Mailman. * It cannot work standalone without Mailman, this cannot replace it (we still need a mailing list server). * 1-day sync (automatic) due to GitHub cron policy (so some latency, acceptable for an archive). Things to do: * Import the SourceForge conversations. There is no plan to push it further for now or to replace the current one. (Let me know if you would like to!) *And also some other information about repository privacy:* Two private repositories are available to Xymon Monitoring members: * |Private|(general information) * |Discussion private|(raw export of Mailman, with private information) → |Discussion public|: generation of the public website Bruno On Thu, 17 Sept 2026 at 12:59, Jeremy Laidman wrote: __ That's brilliant, Bruno! Searchable, and goes all the way back to 2005, in the "Hobbit" days. Nice one! J

1 0

Feedback on using AI/LLMs for Xymon development and reviews
by Bruno Manzoni 14 Sep '26

14 Sep '26

Hi everyone, Here is my feedback on working with AI/LLMs for Xymon: - We no longer code by ourselves; LLMs do it for us. The real skill now is guiding the AI, designing the architecture, and validating the result. LLMs write code better than even experienced C developers, though skilled individuals—including good developers—are still essential to direct them. - We still need to write a specification, like an RFC. - We still need to do reviews to catch problems that a good specification or tests might miss. All this changes the meaning of being a "code author" and shifts how a team should be built. Let me know what you think! Cheers, Bruno

6 7