3 ms·
Not all bugs are created equal. Some bugs are due to an esoteric setup of the user. There in a quasi infinite variation of those in the Linux world. Generally,
by zimbatm 6y ago
Not all bugs are created equal.
Some bugs are due to an esoteric setup of the user. There in a quasi infinite variation of those in the Linux world. Generally, supporting them makes the software more robust, but it's also very likely that you would never encounter that bug yourself.
Some bugs are just support requests. The user didn't understand how to use the software and is confused. Generally the report is quite lacking and it takes a few back and forth to get somewhere.
Some bugs are genuine logic bugs.
I'm sure there are more variations..
- webmaven 6y ago> The user didn't understand how to use the software and is confused. This can be treated as a bug in the documentation.
- zimbatm 6y agoThat's true to some extent. If you see a lot of users having the same issue it might be the case. Sometimes it's also people not bothering to read the documentation. As a maintainer it's also your right to develop a tool just for yourself, and share it for the world. In which case, documentation is not necessarily the priority. And it's fine.
- webmaven 6y ago> Sometimes it's also people not bothering to read the documentation. Yes, sometimes it is. > As a maintainer it's also your right to develop a tool just for yourself, and share it for the world. In which case, documentation is not necessarily the priority. And it's fine. Absolutely fine. Although I'll point out that it is usually a lot easier to get documentation PRs contributed than code PRs.
- webmaven 6y agoI'm being downvoted, but I don't understand why. I said it CAN be treated as a bug in the documentation, not that it SHOULD or MUST be. Edit: more downvotes, on this comment asking for feedback, rather than providing feedback. O_o