Who owns the issue tracker — the maintainer or the user base? If the maintainer is using the issue tracker to prioritize development, they should feel fine abo

Who owns the issue tracker — the maintainer or the user base? If the maintainer is using the issue tracker to prioritize development, they should feel fine about closing issues, especially when those issues are underspecified, ignore the project's contribution guidelines, or are otherwise incomplete. > That's fine, it's quite possible - even likely - that someone else experiencing the same problem will find the issue and be able to add more context. That's not my experience with issue trackers. It's far more likely that underspecified and otherwise problematic issues accumulate until the issue tracker becomes borderline useless. The issue is still there if it is closed, including any contributed but unapplied patches.