News for hackers. Stuff that matters.
Re:Systemd: The Good Parts by 867-5309 on Monday May 17, 2021 @11:48PM (#27191080)
not following
Re:Systemd: The Good Parts by pseudalopex on Tuesday May 18, 2021 @02:16PM (#27198792)
You can't compare the number of stars for different kinds of software.

A large number of open issues means the maintainers can't keep up. 10x more issues mean the problem is worse even if the project has 20x more stars.

Re:Systemd: The Good Parts by TheDong on Tuesday May 18, 2021 @08:54PM (#27203315)
For what it's worth, I also don't think comparing issues between different projects works.

If you have project A, run by a company, which uses an internal Jira instance to track backlogs and developer's selected tasks, but uses github issues to track all user's reported bugs, well, that will have fewer issues than project B, which uses github issues to track backlogs and sprints in addition to bugs.

There's a lot of variability in this. The kubernetes project (~2k issues) has a bot that closes issues after 90 days by default (~9k closed by the bot so far), and without that bot, they'd have way more.

> A large number of open issues means the maintainers can't keep up.

That's not necessarily true. Github doesn't prescribe that every issue is immediately actionable. Perhaps the issue was tagged as "feature-request / help-wanted". Perhaps it is marked as "awaiting additional reporter info" (like logs, or OS), and there's nothing the maintainers can do until the reporter gets them more info.

Whether every issue gets triaged tells you something about whether maintainers are keeping up, but issues that are triaged aren't then always closed, so the number of open issues doesn't tell you much about how many issues are triaged and how quickly.