https://bugs.kde.org/show_bug.cgi?id=226344
--- Comment #7 from rbing...@acm.org --- Mr. Feck, Respectfully, re-read your 2010-02-11 20:08:21 EST post. Expanding your own quote a bit we have "...so I wonder where you see KDE not respecting that variable." "I wonder..." is the governing subject-action phrase here. You wonder/muse/consider/ponder but have not asked action of anyone. Three minutes later at 20:11:51 EST you weaken it even further, effectively appending "...you might...". Pedantic about wording but I had to learn this the hard way in a previous life as an IT sales engineer when requesting information or action from busy, distracted customers or prospects. I and my company's offerings or installed product were some modest to very small fraction of their day job. I learned to structure requests as bite-size "executables" with context info, instruction, desired reportables and a call to action establishing roles/responsibilities. In this bug report context where the reporter will typically be busy, distracted and of modest technical literacy, a structured, firm NEEDSINFO template might be: ###### Please update this bug with: 1) <observation or value acquired through step-step-procedureA > 2) <observation or value acquired through step-step-procedureB > 3) dah, dah, dah Please post back to this bug if you need help with any of the bullet items. Regards. Super KDE Dev 42 ####### Starts with a strong call to action "Please update..." laying responsibility on the reporter or identified party, then a bullet list of "executables" resulting in reportable info, then an escape-help-retry path is offered if one of the executables stalls or fails. Roll your own. Regards, R -- You are receiving this mail because: You are watching all bug changes.
