Yeah, just to be clear I'm not bitching at maintainers, just giving the perspective of a potential company wanting to use a library. Though usually I do try to follow up if I think the software/lib is really nice, but it's often on a personal level, not for my company.

Documentation is pretty boring to write,and not as fun as feature-du-jour, but may be there could be some guidelines about what a basic documentation should have, specially with GitHub it could be straight forward to have a Markdown template for basic doc (Installation, FAQ, Requirements, Contact points, ...), I know I use one.