Re:Turning Off GitHub Issues (2016)
by scrollaway on Tuesday May 23, 2017 @06:48PM
(#14406086)
A thousand times this. Issues are generally a favour your user is doing you and your project. Yes, sometimes they're a waste of time; it's fine to close them if they are, it takes exactly one click to do so. Most of the time however, they're valuable even if you don't fix them: Other devs might see them and fix them for you.
In almost all cases, turning issues off is incredibly counter-productive.
> the person maintaining the code actually knows what it does and how it works
But apparently they're not allowed to decide what works best for their project as far as bug reports.
Re:Turning Off GitHub Issues (2016)
by robotresearcher on Tuesday May 23, 2017 @07:00PM
(#14406166)
I agree with your argument completely.
Just be nice, and your accurate advice is more likely to be useful. That's all.
Re:Turning Off GitHub Issues (2016)
by BugsJustFindMe on Tuesday May 23, 2017 @07:04PM
(#14406194)
> Just be nice, and your accurate advice is more likely to be useful. That's all.
https://en.wikipedia.org/wiki/Tone_policing
My advice is already useful. If someone chooses not to take it because they'd rather tell non-technical users to pound sand, then I hope their project suffers for it.
Re:Turning Off GitHub Issues (2016)
by robotresearcher on Tuesday May 23, 2017 @07:09PM
(#14406231)
There is an obvious meta comment to make here that I leave as an exercise for the reader.
Re:Turning Off GitHub Issues (2016)
by BugsJustFindMe on Tuesday May 23, 2017 @07:17PM
(#14406290)
Nah, you're probably mistaken.
Then, fine, tone police, I'm not classy.
I am, however, a FOSS developer who understands the value of non-technical contributions to a project.
Know which kinds of bugs don't get fixed? The ones your users never tell you about because you decided to make it hard to report them.