3 ms·
I think the problem is that most people (both users and developers) mistake an issue tracker for a world-writable TODO list. If something goes wrong, it imposes
by skybrian 10y ago
I think the problem is that most people (both users and developers) mistake an issue tracker for a world-writable TODO list. If something goes wrong, it imposes an obligation that someone fix it.
Instead I'm in favor of the fire-and-forget feedback form. This makes it clear that feedback is a pure gift with no obligations on either side. Users: you don't need to look for duplicates or come up with a way to reproduce it. Just talk about what happened to you. Developers: it's just data, do with it what you like. Go wild, run machine learning on it.
Okay, sure, add optional contact info, so the developers can ask for a repro case if they think it's particularly interesting.
(There was a great Paul Ford article about Internet feedback but my searches aren't finding it.)