> I just wish more projects took the time to making this page more useful. When you create a "good first issue", think of it as paying it forward. You enter a contract with a fragile newbie; be precise, helpful and unassuming.
I love this. It’s no surprise that OSS projects need the occasional backlog grooming.
> But I've found this page to be downright helpful in most cases.
How many projects have actually had productive contributers join out of an abstract desire to contribute.
Whenever I've contributed to outside projects, my motivation had been to avoid needing to maintain a fork. And whenever projects I'm a main on have had outside contributers, they very clearly had clear objectives they wanted the project to meet.
The much more important instructions for new developers is how to contribute guidance. Along with generally good documentation and design so they can actually make the changes they want to make.
There’s an additional difficulty here which is the actually good first issues tend to be completed early in their existence, so the long-term steady state is issues that are much more difficult for some reason or another (even if they aren’t stale)
6 comments
[ 2.6 ms ] story [ 25.8 ms ] threadI love this. It’s no surprise that OSS projects need the occasional backlog grooming.
> But I've found this page to be downright helpful in most cases.
Perhaps you meant to say “UNhelpful”?
Whenever I've contributed to outside projects, my motivation had been to avoid needing to maintain a fork. And whenever projects I'm a main on have had outside contributers, they very clearly had clear objectives they wanted the project to meet.
The much more important instructions for new developers is how to contribute guidance. Along with generally good documentation and design so they can actually make the changes they want to make.