3 ms·
Thanks for the kind words! You have an interesting idea, but it seems tricky to pull off in practice. To be clear, I'm not necessarily trying to say that low e
by burntsushi 7y ago
Thanks for the kind words!
You have an interesting idea, but it seems tricky to pull off in practice. To be clear, I'm not necessarily trying to say that low effort issues _are_ a waste of my time, but rather, that is sometimes how _I feel_. I think it would be good to collectively reduce their occurrence---I'm not sure how---but sometimes the choice isn't between "low effort issue" and "high quality issue," but rather, "low effort issue" and "none at all." In the latter case, I'm not sure which I would prefer. Certainly, sometimes low effort issues really do lead to productive outcomes.
It's tough and it's not something that has an easy answer. Some part of it is me overcoming how negatively I feel about them and another part is perhaps others spending a bit more time filing good issues. At least, in my opinion anyway!
- dancek 7y agoI didn't mean to imply how you think or feel. Sorry if my comment came off that way. Maintainer burnout is a real problem and I personally would run a real risk if I ever released something worthwhile. I agree that the idea is raw and difficult to implement, but we should think about these things as a community (ie. I don't have the energy to do anything about it, but I'm hoping someone would).