3 ms·
Opinions of Mozilla aside; the reason maintainers do this is because people google bugs or "why can't I do this in x" and they land on GitHub issues. They then
by oooyay 2y ago
Opinions of Mozilla aside; the reason maintainers do this is because people google bugs or "why can't I do this in x" and they land on GitHub issues. They then pepper those issues with either low-tier comments like "zomg +1 op" or totally unrelated comments. GitHub doesn't have a way to differentiate a random Internet user who arrived on a big through an internet search and someone who is a long time user but not a contributor. This, lock to maintainers happens once you know the cause, effect, and what it takes to fix it.
- beeboobaa3 2y ago> They then pepper those issues with either low-tier comments like "zomg +1 op" or totally unrelated comments I agree it's annoying, but you can also just unsubscribe from the issue if you're no longer interested in community feedback. > This, lock to maintainers happens once you know the cause, effect, and what it takes to fix it. This is not really my experience. Usually it goes more like this: 1. Person makes issue 2. Lots of people respond to the issue because they experience it as well 3. Developers either don't care, or fail to grasp what the users actually want 4. More people pile on over the course of months/years while no resolution exists 5. Developers get annoyed, and lock the issue 6. Either they already did, or some point later the developers introduce a "close old issues with no response" bot 7. Issue is locked, cannot get responses 8. Issue gets closed 9. Open issue count goes down 10. Yay!