Yeah, very few people are good documentation writers. After writing up a lot of maker projects I found that I like to do docs, and that makes me also more demanding regarding the quality of the docs I need to feedback on. It would be great if people would put more time in it to become better, and another reason why I like sort-of self-documenting tools (e.g. Rust, where documentation is taken seriously from the beginning of the project).<p>I didn&#x27;t mean everyone can update the docs, rather send feedback by patch&#x2F;pull request of actual changes instead of writing in email with words that &quot;Rewrite header 1 to be X, add label Y to figure 2, and add date into footer&quot;. Currently bloody Word Docs and PDFs are sent around twice a day for &quot;please reply with your comments&quot;, and things get lost between emails, changes that were applied before disappear because someone edited the wrong version of the Doc, or exported into PDF in the wrong way... All in all, changes shouldn&#x27;t happen in email text, IMHO.<p>Whether anyone can edit the docs - I&#x27;d actually like to see that (even if I haven&#x27;t said that originally). Currently even the people who are charged with maintaining the docs update it only when pushed, I think in most places you&#x27;d be lucky if anyone touches it. On the other hand, an empowered team where anyone can access improve on things is a very different feeling, that&#x27;s what creates successful stuff, IMHO. And with version control failure is cheap and easy to fix, so there&#x27;s very little downside. Think of large public projects like OpenStreetMap or the Embedded Linux Wiki at <a href="http:&#x2F;&#x2F;elinux.org" rel="nofollow">http:&#x2F;&#x2F;elinux.org</a> It works out pretty well for them with no big trouble, and they literally let everyone change things (not just project members).