Apologizes for top-posting... Is this conversation supposed to be public? It looks like it got unintentionally pulled into kde-devel by Harald and now is visible for everyone to see. I get the feeling this was being handled in a private mailing list most likely since Harald's message is the first one I see in this chain.
On Thu, Jul 3, 2025 at 11:54 AM Christoph Cullmann <christ...@cullmann.io> wrote: > > Hi, > > On Thursday, July 3rd, 2025 at 18:50, Łukasz Wojniłowicz > <lukasz.wojnilow...@gmail.com> wrote: > > > > > > > > > On 25-07-03 18:33, Reindl Harald wrote: > > > > > > Am 03.07.25 um 18:27 schrieb Łukasz Wojniłowicz: > > > > > > > > Hi all, > > > > > > > > > recently I got an answer like at https://bugs.kde.org/show_bug.cgi? > > > > id=506334#c12 and was shocked. > > > > Being accused of being insulting, while trying to find the root > > > > cause of the issue and then commanded for this bug not rolling out > > > > perfectly from the beginning. > > > > All with the mix of all caps words. > > > > Anybody subscribes to this way of expression? > > > > > > > > > I'm not sure, if that's the right place. The Code of Conduct site at > > > > https://kde.org/code-of-conduct/ doesn't contain any address for > > > > reporting incidents. > > > > bugreports without steps to reproduce and no backtrace are simply > > > > useless - how do you imagine anybody to work with that? > > > > > Did you look into the report? In the first comment it has backtrace and > > description of activity when it crashes. It looked like random then. > > The 'STEPS TO REPRODUCE' is just the quote of what is in the template, > that is repeated once more with 'EXACT' added. > > That might not be the most gentle comment I have ever seen, but IMHO that > > is just not polite and no CoC incident. > > We are all human and I would assume one can bit a bit lenient with the > developers > that actually at all care and read bugs and often stumble above missing > points. > > Greetings > Christoph > > > > -- > > Cheers, > > Łukasz
