Menu

How I Choose Which Open Source Issue to Work On (After Picking Wrong Ones)
📰

How I Choose Which Open Source Issue to Work On (After Picking Wrong Ones)

DEV Community: career·VINAYAK GOTE·10 days ago
#dIEqV52I
#devtocareer#devto#dev#merged#format
Reading 0:00
15s threshold

In my last post I wrote about a PR I closed on purpose, because the maintainers were already fixing the same bug. That was a lesson in picking issues better. Over a few months and several repos, I settled on a simple routine. This post is that routine, so you can skip the mistakes I made.

Step 1: Check that the project is alive

Before I read any code, I open the repo and look at three things:

Were PRs merged in the last few weeks?

How fast do maintainers reply on issues and PRs?

Do outside contributors get their PRs merged, or only the team?

A project with no replies is a waiting room. I would rather spend my time where someone will read my work.

Step 2: Check that nobody else is on it

This is the step I skipped with Riptide.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.