https://bugs.kde.org/show_bug.cgi?id=396675
ocumo <kxk-ocumoatbugs...@lugosys.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
Version|4.1.0 |unspecified
--- Comment #8 from ocumo <kxk-ocumoatbugs...@lugosys.com> ---
Sadly, this project behaves like a one man's show, despite of what other
enthusiastic contexts say, where even big names like Intel or Google are
mentioned. The truth is, when the leader is down (for understandable and
worrying reasons), there is a huge impact. Not a criticism, it's hard reality,
as has been rather rudely expressed several times in comments in bug reports.
Some hard facts that don't play nicely about krita's "team" response to this
serious issue:
1. Despite overwhelming demonstrations that this problem will (and I bet that
it does) affect others in a valid use case, there has been no noticeable
interest in this bug.
2. Not only there is lack of user's interest or, more likely, lack of knowledge
and stomack for entering the ugly world of bugs reports. The problem extends
more importantly to krita's team. "Doesn't affect me? Then too bad."
Fact, there are not enough people to even look at what has cost me dozens of
hours of troubleshooting and reporting, late at night, making huge efforts to
painfully demonstrate a real problem in real case scenario. It is announced in
some places that there is a team, but there is only one person looking at this
bug report. With indeed only one person looking at this, it is impossible to
manage the workload, and one could hardly blame such overwhelmed person, only
wish him to take care of his health seriously. This is absolutely insane.
3. I have lost the count of the times I have been told that this is not a
krita's code problem.
Frankly, it's beyond irritating that such statement would be thrown in a bug
report. Who is interested in fingerpointing? How old are we, 6? Who's problem
it is that your product doesn't work in a VALID use case? Not a fantasy, not an
edge case. A normal case. If krita doesn't recognize the strokes of my
toothbrush on my monitor, I won't blame you or open a ticket on Oral-B's
customer support or on the supermarket where I bought it for 2.35 Euros.
I can't say this clearer or frequently enough: I do not care "who" forgot a
semicolon or who wrote an idiotic API or 3rd party program or which criminal
manufactures a disastrous piece of hardware. As long as that thing is required
and supported by your product, then you own that problem. Your product doesn't
work in a __valid_use_case__. If I wouldn't have proven a *valid use case*, I
wouldn't be wasting my time here, late at night and with bad health.
Why is it so hard to say: "yes, it is _our_ problem, because it affects _our_
product and _our_ users." ? I will never get it. Have you ever had a problem
with your new car? would you accept they do nothing because they blame China,
which produces such bad aluminium that your engine cracked? What about your
stinky smoking "non-polluting" Volkswagen?
Whether the root cause is bad Ubuntu, bad KDE, bad Qt, Wacom, Nvidia, bad
Goverment, the NSA or climate changes: the only and absolute workable truth is
that krita is _the_thing_ that doesn't work in a well documented, normal
_valid_use_case_scenario_, demonstrated to exhaustion, literally. I don't see
any interest to admit it and _document_ it for the existing and potential
users. It seems it isn't interesting except to myself.
No matter how moronic Linux, Ubuntu, Debian or Qt might be and how clean and
elegant krita's code might be, it is krita's team lack of taking ownership of
well demonstrated, well described valid failure modes and not providing vital
information in the right places, what deeply frustrates any good intentions and
all hard efforts I have made to help. No, it has nothing to do with work load,
not after nearly a year of so much discussion and information offered from my
side in the same topic.
4. No matter how overwhelming the work load of a one man's show might be, this
8 months late "response" is inequivocably poor and frustrating because you have
known the issue and stated that you know the solution since very long time
already (https://bugs.kde.org/show_bug.cgi?id=392251#c24) and yet no follow up
action was taken to at least inform the users, other than "we need to think" in
an obscure comment deep down in a long thread of some bug report more than half
a year ago.
Please no blame on overwhelming work load and loneliness. That has been
demonstrated countless times, not in the kindest manners, which I reckon why,
having been myself victim of burnout. So please, don't. I have been in worse
situations than that, truly alone and without any resources at all, no Google,
no Intel, no money. Only pressure. One myocardial infarct later, I should know.
Believe me man, you don't want to be there. I pray that you won't.
If you are the only one reading and taking care of these reports and krita's
problems, I sincerely wish that you rather focus more on your own health and
sanity, and shutdown this nonsense bug report system.
But first!! please stop encouraging people to test krita and report bugs.
That also should help others to keep their sanity and stop wasting their
valuable night hours and brain power in useless contributions like those I have
made.
--
You are receiving this mail because:
You are watching all bug changes.
