heh, i’ve seen almost exactly this break a dev before. it was the ion3 dev, tuomo valkonnen. he was probably never entirely OK, but eventually he ragequit opensource, installed windows, deleted all his opensource projects and went incommunicado.
what pushed him over the edge was distros shipping packages of somewhat older versions of his windowmanager (so, not updating their packages as soon as he released a new stable version) and then users filing bugreports for bugs he’d already fixed.
I totally get the frustration of getting pointless bug reports.
I’ve seen many repos with a “you must reproduce your issue on the version we release here to report” policy, I wonder if that could be a solution.
Maybe together with a GitHub bot to scan logs posted on the issues and inform the reporter about that…
heh, i’ve seen almost exactly this break a dev before. it was the ion3 dev, tuomo valkonnen. he was probably never entirely OK, but eventually he ragequit opensource, installed windows, deleted all his opensource projects and went incommunicado.
what pushed him over the edge was distros shipping packages of somewhat older versions of his windowmanager (so, not updating their packages as soon as he released a new stable version) and then users filing bugreports for bugs he’d already fixed.
I totally get the frustration of getting pointless bug reports.
I’ve seen many repos with a “you must reproduce your issue on the version we release here to report” policy, I wonder if that could be a solution.
Maybe together with a GitHub bot to scan logs posted on the issues and inform the reporter about that…
he had the policy, he just couldnt deal with the idiots who refused to read it