Project direction and next steps – GitHub migration and branch model

Hi Stef,

Yes, I think it is quite hard to follow the mailing list across multiple subjects. Many times we end up with the same information repeated, or even contradictory information.

I’m not using the GitHub wiki because I was told that a repository wiki is not indexed by search engines (e.g., Google). In case someone wants to build a wiki, I created a dedicated repository called xymon-wiki, which can be indexed by search engines and is published as a website.

Also, we can pin three issues so they stay at the top of the Issues list. We should also reconsider issue titles and scope (more precise vs. more general), and ensure each issue includes enough context to remain clear over time. Potentially, we could maintain a single “index” issue that tracks and links to the key topics.

For problem that are not "Code Problem", I did create some years ago a demo "xymon-problem" repo. I need to clean it up.

In the "private" repository, I have also reserved several channel names as placeholders for potential future use on Telegram (easy API/bots) and Signal (high security).

I don’t have any problem keeping things as they are now. I see this as an iterative process: if a step makes things better, that is already a good outcome. It doesn’t have to be perfect.

Thanks for trying to make things better.

Bruno