News for hackers. Stuff that matters.
Re:Turning Off GitHub Issues (2016) by Etheryte on Wednesday May 24, 2017 @06:56AM (#14409026)
I think you're trying to paint this too black and white. It's perfectly reasonable to be interested in supporting only the proactive user base of your project – that way both parties give and gain something.
Re:Turning Off GitHub Issues (2016) by BugsJustFindMe on Wednesday May 24, 2017 @08:43AM (#14409561)
> It's perfectly reasonable to be interested in supporting only the proactive user base

If you only care about the bugs that someone else fixes for you, then you don't actually care. They do, and you're just pretending. It's perfectly reasonable to stick your fingers in your ears and go "LALALALALALALA" instead of listening to reports about bugs in your product the moment you stop giving a shit about it having bugs. A competent person who actually gives a shit isn't willing to put their head in the sand like that.

Re:Turning Off GitHub Issues (2016) by jasode on Wednesday May 24, 2017 @09:00AM (#14409671)
>If you only care about the bugs that someone else fixes for you, then you don't actually care.

You're mischaracterizing the author's post. Notice that the author specifically wrote:

+ "Fork the repo, add a failing test."

+ "Add an example in the repo that illustrates the bug."

Neither of those requests is "fixing" the bug for the author. Maybe those tasks in your opinion is asking too much of users -- and that's fine to feel that way -- but it's obviously false to say that submitting bug reproductions actually fixes the bug. It certainly doesn't.