[Exception request] OmniSight DEV / Ready For Testing candidate #16653
ApplicationOmniSight is a self-hosted infrastructure monitoring dashboard for Proxmox, VMware, Linux, Docker, Kubernetes, SNMP devices, storage systems, firewalls, databases, and external services.
Requirement status — requesting a DEV/testing exceptionI want to be explicit that OmniSight does not currently satisfy the normal application thresholds:
I will not check requirement boxes that are not true. Before opening a PR that automation would immediately close, I am asking whether maintainers would consider a ProxmoxVED / Ready For Testing exception, similar in scope to the current PVE-UPS development test. I understand that PVE-UPS is maintainer-sponsored and still in DEV, not evidence that the production requirements were removed. Integration readinessThe prepared branch contains only the required files:
It follows the current ProxmoxVED conventions:
The scripts pass Bash syntax, JSON, static contract, and upstream OmniSight LXC smoke checks. A fresh install, advanced install, service/UI check, update, and persistence test on real Proxmox VE would still be collected before promotion. If a maintainer considers the project useful enough for early DEV testing, I can open the matching ProxmoxVED issue and PR immediately and help collect test reports. If not, I will wait until the published criteria are met and will not repeatedly ping maintainers. AI assistance disclosureThe contribution scaffolding was prepared with OpenAI Codex (GPT-5, high reasoning) using the repository's |
Replies: 2 comments
|
Hi, i can see you already prepared a script that can be integrated into our repo. Please make a PR to our testing repo and reference this discussion in it. One of the maintainers will take a look and if we agree to make the exception, we will push it to main repo. |
|
Yes, I came across that project on Reddit, where it gained significant momentum. I personally liked the project and thought it provided a lot of value to Proxmox users with a UPS, which is why I decided to create the script and discuss it with the maintainer. Ultimately, we are the people maintaining and contributing the code, so we decide what we want to include in the repository. For community-submitted projects, the published requirements therefore apply unless we, as maintainers, explicitly decide to make an exception. PVE-UPS is not intended to establish a general exception to those requirements, as it is a project that was specifically sponsored by a maintainer and is still being developed and tested. That said, OmniSight looks really good, and we would be happy to take another look at it later. Once it meets one of the two currently unmet requirements, so that only one requirement remains outstanding, feel free to submit it to the testing repository. From there, we can evaluate it further and see whether it makes sense to make an exception for the remaining requirement. Otherwise, once all requirements are met, you can of course submit it through the normal process. |
Yes, I came across that project on Reddit, where it gained significant momentum. I personally liked the project and thought it provided a lot of value to Proxmox users with a UPS, which is why I decided to create the script and discuss it with the maintainer.
Ultimately, we are the people maintaining and contributing the code, so we decide what we want to include in the repository. For community-submitted projects, the published requirements therefore apply unless we, as maintainers, explicitly decide to make an exception.
PVE-UPS is not intended to establish a general exception to those requirements, as it is a project that was specifically sponsored by a maintainer and is still being de…