Seems like I already explained this kindly enough. Here's my last shot.
To most, no terrible product is made good by having quality and clear documentation, change logs, tutorials, release cycles, roadmaps, etc. Most casual users never even look at any of that stuff. They expect things will be obvious and just work. If they don't, they give up.
What is obvious to all users, not just the most basic ones: it is painfully annoying to use any terrible product, where the developers are not given time and space to do their best work. Especially in beta, when there are big and frequent changes that periodically make whole swaths of docs, tutorials, release cycles, roadmaps, etc. obsolete and useless, working on stuff like that is an annoying waste of effort.
The quality of an OS is not purely in its code, but it is mostly in its code.
While one can have both quality communication and a quality product, if I had to allocate development resources of a project in beta, I would allocate them to product, not communication. Especially because bad communication can be much worse than no communication.
The impetus for my comments was the fact the other people brought up marketing, and I also get why they stopped replying.