Skip to Main Content
Talk Beginner

Your First PR Doesn't Have to Be Code

Proposal status is Rejected
Session Description

There is a story that open source tells about itself: that contribution means code. Pull requests, patches, commits. The mythology of the lone developer fixing a bug at midnight and submitting it upstream. Documentation, if it appears in this story at all, is the thing someone writes after the real work is done.

This talk is about what that story costs — and what the alternative looks like in practice

Documentation has always been a real entry point into open source. It is how many people — including me — made their first contribution, found their first community, and stayed. It does not require a development environment. It does not require knowing the codebase. It requires curiosity, attention to detail, and the willingness to write down what you just learned so the next person does not have to figure it out alone. These are not lesser skills. They are the skills that keep projects alive long after the initial burst of engineering enthusiasm fades.

But the path is harder than it needs to be. Good first issues that are not actually good for first-timers. READMEs that do not mention documentation as a contribution type. Review processes designed for code patches that handle prose contributions awkwardly or not at all. Maintainers who genuinely value documentation but have never thought carefully about how to signal that, onboard someone into it, or review a writing contribution constructively.

This talk speaks to both sides of that gap. For new contributors, it is a practical guide to finding your footing in a FOSS project through documentation — where to start, what to expect, how to make a contribution that gets accepted and makes you want to come back. For maintainers, it is an honest look at what your project looks like from the outside and what small, concrete changes make the documentation contribution path feel genuinely welcoming rather than technically available.

Drawing on my experience as a technical writer at Red Hat, an open source contributor, and someone who mentors new doc contributors, this talk is full of real stories — of first contributions that landed, of ones that didn't, and of the tiny moments that decided which way they went.

References

Session Categories

Contributing to FOSS
Technology / FOSS licenses, policy

Which track are you applying for?

Documentation & Technical Writing

Speakers

Yash Guddeti
Yash Guddeti Technical Writer | Energy Exemplar

I am a Technical Writer, community leader, and advocate for open knowledge who is passionate about helping people understand, adopt, and contribute to technology. My work focuses on creating documentation, user guidance, and AI-assisted knowledge experiences for complex enterprise software, making sophisticated systems more accessible to diverse audiences.

Kalyani Desai
Kalyani Desai Technical Writer | Red Hat

I am a Technical Writer, Content Engineer, and Information Developer at Red Hat, working at the intersection of technology and communication. I focus on making complex developer documentation clear, accessible, and genuinely useful — currently leading documentation for Red Hat OpenShift Serverless and Red Hat OpenShift Serverless Logic, and maintaining their upstream open source projects: Knative, Kogito, and SonataFlow.