3 ms·
It’s definitely laziness, but they’ll argue it’s lack of time (and lack of knowledge is really just too lazy to self inform). It’s not just a problem with open
by rapind 4y ago
It’s definitely laziness, but they’ll argue it’s lack of time (and lack of knowledge is really just too lazy to self inform). It’s not just a problem with open source, but commercial product support as well.
I’ve had customers who invest no effort in a support request then get annoyed when we try to politely extract what the actual issue is from them.
For open source I’d lean towards a policy of 0 investment from you, then 0 investment from me. You can always archive low effort issue reports to peruse at a later date when you have free time to see if you can discover something meaningful in them.
- tennis_80 4y agoI agree with this. In my experience often people want to push the problem to someone else - if you can say in your team status update "I've opened a ticket with X, waiting on them to solve the issue", you can get away with being blocked. If the aforementioned ticket is closed for lack of detail, it becomes more obvious to others on said team that the person needs to do more exploratory work.