4 ms·

That issue does not really work in GNOME's favor, based on reading that I'd say they're being pretty toxic.

marcusb 1y ago
We’ll have to agree to disagree about that. The clown-emoji guy is out of line (at least, I wouldn’t respond to a user that way,) but the reporter: * opens up his bug report passive-aggressively complaining about not getting a response to his emailed report, which he sent to a completely unrelated domain * immediately fished for a bug bounty payout * submitted his report against a 2.5 year old release, wasting maintainer time and then pushes back that because it came with his preferred distribution[0] that made it the Evolution maintainer’s problem. * when the maintainers pointed out this was a dependency problem, accuses them of “buck passing” and demands they warn users of specific distributions about the problem he reported, which is, of course, completely impractical for them to do. * does not engage at all with the Webkit developer who is trying to explain what the problem is and why fixing in Webkit is the right thing. * demands one of a selected list of fixes from the maintainers. Note: if his suggested fixes are so simple, a PR at this point implementing one of them would have probably been more productive than what he did post: I understand that this is completely out of your power to do anything about, and that it is also completely out of your power to put a notice in the UI about the functionality not working for privacy purposes. Please add clown and face-palm emojis to this comment as per my other comments, to indicate you have read it. He didn’t do himself any favors and, IMO, doesn’t have much of a leg to stand on to complain about the tone of the response he got. He got back what he put out. 0 - a distribution, by the way, that is notorious for distributing hacked up out of date software. See: the OpenSSH key saga as well as projects like XScreensaver that have Debian-specific FAQ entries telling their users how to get reasonably up to date software (https://www.jwz.org/xscreensaver/faq.html#upgrade https://www.jwz.org/xscreensaver/faq.html#upgrade)

We’ll have to agree to disagree about that. The clown-emoji guy is out of line (at least, I wouldn’t respond to a user that way,) but the reporter: * opens up his bug report passive-aggressively complaining about not getting a response to his emailed report, which he sent to a completely unrelated domain * immediately fished for a bug bounty payout * submitted his report against a 2.5 year old release, wasting maintainer time and then pushes back that because it came with his preferred distribution[0] that made it the Evolution maintainer’s problem. * when the maintainers pointed out this was a dependency problem, accuses them of “buck passing” and demands they warn users of specific distributions about the problem he reported, which is, of course, completely impractical for them to do. * does not engage at all with the Webkit developer who is trying to explain what the problem is and why fixing in Webkit is the right thing. * demands one of a selected list of fixes from the maintainers. Note: if his suggested fixes are so simple, a PR at this point implementing one of them would have probably been more productive than what he did post: I understand that this is completely out of your power to do anything about, and that it is also completely out of your power to put a notice in the UI about the functionality not working for privacy purposes. Please add clown and face-palm emojis to this comment as per my other comments, to indicate you have read it. He didn’t do himself any favors and, IMO, doesn’t have much of a leg to stand on to complain about the tone of the response he got. He got back what he put out. 0 - a distribution, by the way, that is notorious for distributing hacked up out of date software. See: the OpenSSH key saga as well as projects like XScreensaver that have Debian-specific FAQ entries telling their users how to get reasonably up to date software (https://www.jwz.org/xscreensaver/faq.html#upgrade https://www.jwz.org/xscreensaver/faq.html#upgrade)