As someone who runs a couple small projects with large userbases, having multiple issue queues across multiple platforms is a massive organizational hassle. Having one canonical place for issues makes life easier for all parties.
With that said, if you disable issues on a system, make sure you have prominent documentation that says "Submit issues to XXX". Otherwise, it's confusing.
And for the users. Given that it's fairly technical software, it's reasonable to expect that folks would search the issue queue before submitting an issue. If the issue queue was split across multiple sources, issues would exist in one system and not the other.
Sorry if you disagree, but giving clear instructions about how to report issues and limiting vectors is fair, logical, and incredibly common and a best practice.
If said casual user doesn't want to bother finding where to report issues (which a competent maintainer would surely document in the main README), there's also a fairly good chance it's not a big deal to begin with or that the explanation is vague/unactionable, at least from my personal experience.
Comments
Disabling issues can feel hostile, though I understand why large projects might do it because idiots abuse the system.
But when I go to a project on Github to report an issue and I can't, then I can't help but think "well fuck you too."
As someone who runs a couple small projects with large userbases, having multiple issue queues across multiple platforms is a massive organizational hassle. Having one canonical place for issues makes life easier for all parties.
With that said, if you disable issues on a system, make sure you have prominent documentation that says "Submit issues to XXX". Otherwise, it's confusing.
It makes life easier for you.
It doesn't make life easier for the casual user of your software who just wants to report one issue.
And for the users. Given that it's fairly technical software, it's reasonable to expect that folks would search the issue queue before submitting an issue. If the issue queue was split across multiple sources, issues would exist in one system and not the other.
Sorry if you disagree, but giving clear instructions about how to report issues and limiting vectors is fair, logical, and incredibly common and a best practice.
If said casual user doesn't want to bother finding where to report issues (which a competent maintainer would surely document in the main README), there's also a fairly good chance it's not a big deal to begin with or that the explanation is vague/unactionable, at least from my personal experience.
This is also how I feel when I want to report an issue, but to do so I need an account with Peer Pressure Inc.