Does your open source project need better documentation? Do you wish that new users could on-board to your software more easily? Do you feel that your contributors are discouraged from documenting their code?
Assuming that the answer to at least one of these question is a bright flashing neon YES, this talk goes through the basic principles of technical communication in the context of open source projects. Themes include tone, style, grammar, workflow, and tools.
This talk is based on my personal experience as a technical writer and scrum master in the software industry for the past 6 years, as well as on my adventures in the open source communities for the past year.
**This version of the talk was presented at the KDE Akademy in Brno, September 2014**