
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
5858 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.

187 Listeners

1,705 Listeners

288 Listeners

2,011 Listeners

555 Listeners

2,143 Listeners

1,391 Listeners

626 Listeners

583 Listeners

1,028 Listeners

418 Listeners

985 Listeners

8,077 Listeners

175 Listeners

139 Listeners