The Devil always needs my help. But that's just me. YMMV
Realistically, the point I'm trying to make is that documentation, like much of the open-source world, relies on circular arguments. The docs are fine, because if they weren't someone would fix them. There are no major bugs, because if there were someone would fix them. It must be secure, because lots of people must have audited it.
Those arguments probably hold water if your project is oriented at people who write code and build applications for a living. Everyone else wants it to "Just Work(tm)".
I recall someone I knew a long time ago saying that he didn't care how his car worked. If it was powered by "voodoo squirrels" (his words), that was fine with him -- as long as it got him where he was going.
Documentation, like bug fixes and security audits, are things that fall into the "Just Works" category.
The key message that I tell people about open-source software: "If you break it, you get to keep both halves." Maybe you'll find what you need and someone to help you, but I only trust very mature and stable projects for critical things, and your definition of critical may vary from mine. A big portion of RedHat's and WRS' business model is to provide that support to make it Just Work on-demand.
There's a parallel argument for Android vs iOS, if anyone wants to get into that.
As for your original "doing it wrong" comment -- that's entirely dependent on what they are trying to do. If they are trying to create a project with an ecosystem of developer support, then they're probably on the right track. If they want to create a solid and usable piece of software... well, that's why a lot of people get paid to write code, write docs, do security audits, etc. etc.