What a Small Improvement to Vite+ Teaches Us About Getting Started with OSS Contribution
Every day, our development relies on the help of the many OSS projects that surround Vue. I'm sure a lot of people feel like "I want to contribute to OSS, but it seems hard."
But those little "I wish this were improved" moments you notice as a user? You can actually fix them yourself, with your own hands.
I responded, via a PR, to one user's voice about Vite+'s `vp migrate`: "it's hard to tell why this file needs to be migrated, because there's so little information."
In this lightning talk, centered on Vite+, and drawing on real examples of PRs I've sent to other OSS projects like Storybook and Oxc as well, I'll introduce how to find things worth contributing to, along with the etiquette of small OSS PRs — keeping each change scoped to one thing, linking it to an issue, and how to write the PR itself. I'll also touch on where to draw the line between what you hand off to an AI agent (like Claude Code) and what you take responsibility for yourself.
All of this, including making use of AI, isn't any different from your everyday work — no special skills required. Take home a way to take that first step, for the sake of the next person after you.
hakshu
What a Small Improvement to Vite+ Teaches Us About Getting Started with OSS Contribution
Every day, our development relies on the help of the many OSS projects that surround Vue. I'm sure a lot of people feel like "I want to contribute to OSS, but it seems hard."
But those little "I wish this were improved" moments you notice as a user? You can actually fix them yourself, with your own hands.
I responded, via a PR, to one user's voice about Vite+'s `vp migrate`: "it's hard to tell why this file needs to be migrated, because there's so little information."
In this lightning talk, centered on Vite+, and drawing on real examples of PRs I've sent to other OSS projects like Storybook and Oxc as well, I'll introduce how to find things worth contributing to, along with the etiquette of small OSS PRs — keeping each change scoped to one thing, linking it to an issue, and how to write the PR itself. I'll also touch on where to draw the line between what you hand off to an AI agent (like Claude Code) and what you take responsibility for yourself.
All of this, including making use of AI, isn't any different from your everyday work — no special skills required. Take home a way to take that first step, for the sake of the next person after you.