Two things to think about: One, as the article points out, supporting Maintainers is important. Two, many software engineers don't enjoy writing documentation

Two things to think about: One, as the article points out, supporting Maintainers is important. Two, many software engineers don't enjoy writing documentation. Even if it would make their lives easier. From that perspective, the majority of these complaints revolve around communication. However, this article frames documentation as something only the maintainer should write. Why not make a PR to update the documentation yourself instead of asking the maintainer to do it? Instead of getting frustrated about opening a bug in the wrong place, why not document the right place? If the description around PR criteria doesn't match your experience, why not create a PR updating it to include undocumented requirements?