https://bugs.kde.org/show_bug.cgi?id=401039
--- Comment #3 from ocumo <kxk-ocumoatbugs...@lugosys.com> --- First of all, thank you very much for taking quick actions. I absolutely agree that this is probably the best solution, given the risks of overloading your limited resources. Just for completeness and clarification of your comment: as I wrote above, "I have notified and provided full details to Krita's team in another report (which is only indirectly related)", and here it is: https://bugs.kde.org/show_bug.cgi?id=392251#c20, including attachment with details, and your reply: https://bugs.kde.org/show_bug.cgi?id=392251#c21 . I didn't say it was a dedicated bug report. The original report in that thread is "only indirectly related" but it *is*, and it is explained there why. I didn't include the above links precisely to avoid entering into a pedantic ping pong of evidences and counter evidences, when the main goal was just to alert the team about an important issue with the documentation. Once again, I do not appreciate or indulge discussing semantics over the issues. I notified a problem, with a big deal of details, in a justified context; I got a main developer's attention, plus a direct reply to the specific issue and attached information. That's it. Not enough? Then the reply could have been specific: "Please do such and such to get this moving forward". No, the reply did not say what else I could/should do. So: The reply wasn't good, but the matter of fact is that the notification went through, to at least one notorious member of the team. So: was my job done? Apparently, not! I sincerely hope that you are not telling me that since I didn't write those words in another separate document with another layer of bureaucracy, is reason enough for you to have dismissed the alert. It's like somebody would yell at me that my house is on fire and I would ignore it because it didn't came in a certified letter. I used to work in a very bureaucratic and huge corporation, and yet nobody would ever dismiss a valid, clear complaint just because it was written in the Form A231b instead of the Form A231B. Why even a huge, slow, heavy corporation would get that and a small non-for-profit project wouldn't? I don't get it. That's probably why I get so cranky about this. My experience in the Kde bug tracking system proves me that my perception of a modern agile mindset is not compatible with older paradigms and bad habits that are still popular amongst many projects. It's getting really painful to contribute. Hopefully things get better in the future. Thanks for all the hard work you guys do, I really respect that. -- You are receiving this mail because: You are watching all bug changes.
