
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.

191 Listeners

1,709 Listeners

288 Listeners

2,009 Listeners

554 Listeners

2,145 Listeners

1,395 Listeners

624 Listeners

584 Listeners

1,028 Listeners

419 Listeners

984 Listeners

8,047 Listeners

178 Listeners

137 Listeners