One challenging aspect of managing large @github repos is dealing with issue backlogs. Every mature product has issues that fall into a gray area of "yes this is real, we'd accept a fix but it's so minor it will never really have enough priority for us to fix". Low pri issues.
Over time the count of such issues grows into the hundreds or thousands. Pretty soon you find that these issues are absolutely dominating your backlog. No one wants to open their repo and see 2,000+ open issues but what to do?
Closing these types of issues is not a great solution. That is a strong signal that you don't want a fix here which isn't the case. It's a real bug, it's just not going to meet the bar. It's also the type of issue that can be good "first issue" candidates for new contributors.
Leaving the issues open is also not a great solution because it adds to the overall noise of the repo. It's much harder for customers to find impactful issues when you're searching through a couple thousand low priority issues.
In many ways I wish we could just have a label on GitHub, say "Eternal Backlog", that would cause them to be mostly hidden from the default display. Still accessible with some extra digging but remove it from the general noise.
Overall though have never found a great answer to this riddle.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
