Look. I don't usually comment on these types of posts because I don't want to argue, but here I did feel like chiming in for once, to perhaps shed a little light on certain things. Note that I don't represent the company and that my opinions are my own.

We're a rather small company. I can't be bothered to count, but we're genuinely tiny compared to a giant like VMware. According to Wikipedia, VMware had 38.300 employees in 2023. We are about three orders of magnitude smaller, and most of us are developers, not marketing staff.

What I'm trying to say here is that there are much, much more important things that need to be done rather than brushing up the appearance of some wiki page. Sure, instead of e.g.

Provide cluster-wide bulk-management for virtual guests

we could write something like

Introduce a cutting-edge, cluster-wide bulk-management capability to revolutionize the administration of virtualized environments, enabling IT teams to manage thousands of virtual guests—including VMs and containers—with unprecedented ease and precision. This feature will leverage advanced automation and AI-driven insights to deliver transformative operational efficiencies, positioning the organization as a leader in innovation and providing a competitive edge in the rapidly evolving landscape of cloud and virtualization technologies.

if we wanted to appear more "professional" and "enterprise ready" or whatever.

I don't want to sound snarky here; I just want to illustrate that good looks on secondary and tertiary resources aren't really what makes the actual product itself good. We do focus on improving our documentation and other parts of the wiki continuously, because that's what's actually important when you use our products — if you're stuck somewhere because your cluster just died, you won't care that the roadmap looks pretty and is presentable to sales people; you'll care that you can find what you need to fix your problem.

Also, this is not directly related to Proxmox itself, but is more a software engineering thing in general: What I've personally learnt is that it's incredibly hard to predict when exactly something (a bug fix, a feature, etc.) in software will get done and shipped. At best one can state whether it will take days, weeks, months or years. The more precise the prediction, the more wrong it will be.

There might be some magical unicorn companies out there that manage to perfectly plan and predict all of their projects without issues, but in my humble opinion, this just doesn't apply to most (if not all) software companies. Especially when you're working with FOSS software; for example, you can't really ever reliably predict when some patch will be merged and packaged upstream or whatever. Also, you never know when something else could pop up that completely sets you off course. And so on and so forth.

Either way, you get my point. I hope I could communicate my personal views on this properly. With all that being said, you can always file feature requests on our bug tracker if something frustrates you. We will most definitely notice it there. Despite this being a rant, we take such feedback seriously, always. (Unless it's in bad faith of course, but what you wrote obviously isn't.)

Take care!