
Sign up to save your podcasts
Or


We’ve all encountered technical documentation: Readmes, product manuals, and how-to guides, to name a few. Some are good, some are not so good, and some are less than helpful. Open source communities often need more people to write and update their projects’ documentation—but it’s not an easy task. So why not help out?
In this episode of Compiler, we find out why everyone should write at least a little bit of technical documentation. We speak to people who contributed to documentation to help, to learn, and even to start their careers in open source.
If you want to get involved with Fedora—technical writing included—check out whatcanidoforfedora.org.
By Red Hat4.7
5656 ratings
We’ve all encountered technical documentation: Readmes, product manuals, and how-to guides, to name a few. Some are good, some are not so good, and some are less than helpful. Open source communities often need more people to write and update their projects’ documentation—but it’s not an easy task. So why not help out?
In this episode of Compiler, we find out why everyone should write at least a little bit of technical documentation. We speak to people who contributed to documentation to help, to learn, and even to start their careers in open source.
If you want to get involved with Fedora—technical writing included—check out whatcanidoforfedora.org.

190 Listeners

289 Listeners

2,011 Listeners

374 Listeners

585 Listeners

1,023 Listeners

289 Listeners

318 Listeners

418 Listeners

988 Listeners

8,041 Listeners

181 Listeners

315 Listeners

64 Listeners

142 Listeners