Wow, surprised to see everyone bickering as opposed to giving praise. Just because the author doesn't want you to log issues doesn't mean the project is any less open source... The code is there, if you have a problem fork and submit a pull request. The author is merely stating the fact he can't fix issues by himself and if you find an issue and can help, you should submit a fix.
Calm down people and learn to say thank you every once and a while. This is seriously cool, it's written in Go (which HN has a raging hard on for), what's not to love about this? I'm grateful someone took the time to get this far, now lets take it further.
It takes a lot of effort to get something like this out. Just think of all the things the author could've done with time invested in this. And to make it open source and donate it to the world is just crazy. Props to the author. The naysayers ought to suck it up unless they've poured their free time in an open source project like this.
That's exactly it. It's like being invited to an expensive restaurant and getting a five course dinner for free including drinks and then complaining that the dinner wasn't good enough. It was a free dinner!
Most people don't care to give back to open source, they just want to have something to fix their problem... I am disabling issues from my projects starting today. I think this is a brilliant way to make people realize that work has to get done and if they don't want to do it, they have to as someone personally to do it and it's really a favor! I love it.
Most people don't care to fix Wikipedia articles either. But I really appreciate the people who do. Turning off the discussions behind those pages would be a terrible disservice to the people who do contribute.
Likewise, turning off issues makes it much more difficult for us contributors. You can't search issues to see who's working on what, get advice or guidance from the community for nontrivial fixes, and otherwise have high-level conversations before even touching the code.
For those who just open issues, it's not always about laziness. Sometimes, you just don't have that much invested in a particular project. Personally, I still open issues to projects I use infrequently. I can't justify diving deep into a new codebase, reading their style guide, debugging, fixing the broken code, double-checking my fix, adding the proper tests, and documenting it in every case, but I'd be happy to spend the 5 min to search the issues and post a new one if necessary.
Calm down people and learn to say thank you every once and a while. This is seriously cool, it's written in Go (which HN has a raging hard on for), what's not to love about this? I'm grateful someone took the time to get this far, now lets take it further.