[sword-devel] Windows Utilities
dfhmch at googlemail.com
Wed Jul 24 08:50:02 MST 2013
My question was not about blame. It was about responsiveness.
The CrossWire wiki <http://crosswire.org/wiki/Help:Contents> directs
people to the issues tracker for reporting problems. I'm on the inside of
CrossWire. Imagine how outsiders might feel if they get the same lack of
Had someone in January last year added even the briefest acknowledgement as
a comment on the issue, I would not have asked this question the other day.
I could accept an issue being assigned low priority. I could accept a
request for further details or more persuasive justification.
What is less than acceptable is to be totally ignored. We generally don't do
that with emails, do we?
To make an observation on your other point, it's always been my experience
that when I have provided technical feedback to programmers as a software
tester, they have almost without exception counted that as valuable input.
Indeed, when I retired from NXP Semiconductors in 2009, my colleagues over
in the Netherlands presented me with a signed plaque from their whole team,
acknowledging how much my technical feedback over many years had helped them
to achieve significant improvements for their test systems and software that
we used throughout our product line.
And when app developers are congratulated for their success, the best ones
reply to thank the writer for their kind remarks, and often include a proper
acknowledgement to their team of volunteer testers who have helped make the
app a success.
No programmer worth his salt should see technical feedback as a
discouragement, providing it is given in good faith and with a right spirit.
It helps of course to be accurate and succinct in identifying the problem.
Vagueness is the enemy of good problem reporting.
View this message in context: http://sword-dev.350566.n4.nabble.com/Windows-Utilities-tp4652865p4652906.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
More information about the sword-devel