Actually if you consider open source as proxy for the communication of ideas, writing docs might be seen as the primary goal of any project. Without docs expre

Actually if you consider open source as proxy for the communication of ideas, writing docs might be seen as the primary goal of any project. Without docs expressing what code is supposed to do, a random git repo is just another worthless, opaque pile of buggy spaghetti to any random bystander. With docs, said bystander is empowered with the original intent, and might even extend your idea far beyond what you ever envisioned (aka "the power of open source"). A side point is that many people (myself included) will look for docs first, as some measurable proxy of code quality. Shitty docs often means shitty code or shitty idea.