> 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.
> There are tribes of developers working on something off GitHub (Discord/Email/Whatever) and issues is where end users come and report bugs or feature requests.
Pfft, if only. GitHub has inculcated a generation of developers into using projects' bugtrackers for support requests and general discussion. GitHub issues isn't where work gets done because it's unfit for purpose. GitHub issues is the "our bugtracker is a making list" antipattern in reverse.
> 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.
Perhaps you meant to say “UNhelpful”?
> Perhaps you meant to say “UNhelpful”?
Yes, thanks for pointing it out!
Grafana has this problem in spades. The Curse of Knowledge is very loud sometimes.
> There are tribes of developers working on something off GitHub (Discord/Email/Whatever) and issues is where end users come and report bugs or feature requests.
Pfft, if only. GitHub has inculcated a generation of developers into using projects' bugtrackers for support requests and general discussion. GitHub issues isn't where work gets done because it's unfit for purpose. GitHub issues is the "our bugtracker is a making list" antipattern in reverse.