diff options
Diffstat (limited to 'doc/faq/questions.docbook')
| -rw-r--r-- | doc/faq/questions.docbook | 160 |
1 files changed, 160 insertions, 0 deletions
diff --git a/doc/faq/questions.docbook b/doc/faq/questions.docbook new file mode 100644 index 000000000..1f7db6b63 --- /dev/null +++ b/doc/faq/questions.docbook @@ -0,0 +1,160 @@ + +<chapter id="questions"> + +<title>Asking Questions</title> + +<para>Chances are, you have been linked to this document from IRC or a +mailing list. You've asked a question, and someone has told you that you +need how to ask more effectively. In order to get an appropriate, clear +answer you need to ask an appropriate, clear question in a manner that's +going to provide an incentive for people to take their time to help you. If +you appear to be rude, lazy or use bad or unclear language then chances are +your question will be ignored</para> + +<qandaset> +<qandaentry> + +<question><para>What do I do before I ask?</para></question> + +<answer><para>Read the documentation and &FAQ; for the application. There is +a wealth of &kde; documentation availible both in the help center and +online. A lot of time and effort has gone into this documentation, and +quite often the answer to your question is here. The general &kde; userguide +can be found by typing +<userinput><command>help:/userguide</command></userinput> into your +&konqueror; addressbar.</para> + +<para>Search the web: Usually googling for a specific error message or +searching mailing list archives can come up with a solution for you.</para> + +<para>Try it and see! Look through all the application options, read the +What's this? and tooltips for the ones you're not sure about. If you're +really unsure about an option save your data and then try it. As long as you +use some common sense, you are very unlikely to break anything by clicking +buttons.</para> + +<para>Above all, don't be lazy. If you show the people who you are asking +that you are able to troubleshoot and research in a logical manner, you're +showing them you're a reasonable person who is worth their time to +help. It's your problem and not theirs so the legwork is yours to do. Save +your helpers as much time as you can, they're busy people.</para> </answer> +</qandaentry> + +<qandaentry> +<question><para>Where do I ask?</para></question> + +<answer><para>Usually the best place to ask a question is on the +<acronym>IRC</acronym> channels and mailing lists devoted to user +questions. Don't post simple questions about using &kde; to the devel +channels and mailing lists, these are for technical discussions. Some good +places are #kde on irc.freenode.net, and the &kde; mailing +lists.</para></answer> </qandaentry> + +<qandaentry> +<question><para>How do I ask?</para></question> + +<answer><para>Try to word your questions in a manner that gives the most +information possible and is polite and courteous. Don't ask to ask, just +ask!</para> + +<para>Q: &kde; sucks, it's being slow</para> + +<para>Is not a question that is likely to get you a useful answer. It does +not give any useful information about troubleshooting the problem, and it +starts out attacking the software in a way that isn't productive.</para> + +<para>Q: Since upgrading &kde; on Slackware &Linux; from version 3.2.3 to +3.3.2 using sources, I have noticed it's being really slow — sometimes +applications take up to 20 seconts to launch. I am using the same user +configuration as I had with the previous version, and I have tried as a new +user. I can't find anything about this on the mailing lists or by a google +search. Could anyone point me to some information that could help?</para> + +<para>This question is polite, contains information to help people +troubleshoot the problem and shows your helpers what avenues you have +already tried.</para> + +<para>Don't assume automatically that the problem is the fault of +&kde;. Proceed as though this is your error, otherwise you will quickly +annoy people if it does indeed turn out to be your problem and not +&kde;.</para> + +<para>Use clear language with correct spelling. Watch out for any +ambiguities and make sure you think about what you say before you write +it. If you are asked for clarification, give it as best you can. &kde; is a +project where many of the users and developers are not native english +speakers and if you don't use correct english, misunderstandings may +ensue. Use the language appropriate to the channel or mailing list you are +in — if you don't, people who might have been able to help you may +ignore your message because it is not in a language they understand.</para> + +<para>Include all information that could be relevant, even if you're not +sure. Have you upgraded other software or hardware on your system, +particularly system libraries or a new kernel? These things could affect how +&kde; performs. Even if you cannot see a link, someone else might.</para> + +<para>Don't paraphrase error messages. Paste in the exact error, and if it's +more than a line or two don't paste them directly into an +<acronym>IRC</acronym> channel. Use a paste service like <ulink +url="http://www.rafb.net/paste/"> http://www.rafb.net/paste</ulink>. If you +must type them in by hand, be sure you are 100% accurate. When you provide +faulty information, your helpers cannot help you as easily. </para> + +<para>Follow up on your solution! Tell us if it worked, or if you have +solved it yourself in the meantime. This helps us know for sure if our +solution worked, and helps other users who may be searching mailing list +archives for a solution to the problem themselves.</para> </answer> +</qandaentry> + +<qandaentry> +<question><para>What do I do when told to look elsewhere?</para></question> + +<answer><para>When you're told <quote>google knows</quote> or <quote>google +is your friend</quote> then chances are, you have not followed the above +advice. You've not done your research, and the solution is probably one the +helper knows very well to be easy to find. When you're linked to a +<acronym>FAQ</acronym> or a usermanual don't ever say, <quote>No, I don't +want to have to read this I want you to just tell me</quote>. This is very +bad manners. If you cannot put in the effort to read the document, what is +the incentive for your helper to put in the time and effort to help you? If +you're told to go use google, take it graciously and do so.</para> </answer> +</qandaentry> </qandaset> + +<para>Above all, use common courtesy. &kde; users and developers are usually +volunteering their time out of an already very busy schedule, and like to +know that you are appreciating that they are helping you for free. Be +polite, say please and thank you and try to be pleasant and +friendly. </para> + +<para> Does this seem like a lot of trouble to ask a question? If you want +to be able to feel that people owe you an answer or support, then you're +quite welcome to pay for commercial support from companies that support +&kde; on &UNIX; platforms. If you don't want to pay money, then pay the +people who do this for free with your politeness and appreciation :)</para> + + +<para>If you think the answer to your question should be included in the +&kde; &FAQ; please feel free to submit any patches or suggestions to the +&kde; &FAQ; Maintainer, at <email>faq@kde.org</email></para> + + + +</chapter> + +<!-- Keep this comment at the end of the file +Local variables: +mode: xml +sgml-omittag:nil +sgml-shorttag:nil +sgml-namecase-general:nil +sgml-general-insert-case:lower +sgml-minimize-attributes:nil +sgml-always-quote-attributes:t +sgml-indent-step:0 +sgml-indent-data:true +sgml-parent-document:("index.docbook" "book" "chapter") +sgml-exposed-tags:nil +sgml-local-catalogs:nil +sgml-local-ecat-files:nil +End: +--> |