Asking Questions

Revision as of 14:01, 25 August 2008 by Annew (Talk | contribs) (New page: Here are a few tips on asking questions, especially in #kde on Freenode, in a way that is more likely toget answers: * Don't ask to ask, just ask: #kde is a user support channel, so w...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Here are a few tips on asking questions, especially in #kde on Freenode, in a way that is more likely toget answers:

  • Don't ask to ask, just ask: #kde is a user support channel, so we expect your questions - go right ahead :-).
  • Be ready with any relevant details about your system: What distribution (what version?), what version of KDE you're running, how you installed it and so on. You probably won't need to give all of this information straight away, but you should have it available in case someone asks.
  • Try to do some troubleshooting yourself before asking: Google is your friend (entering error messages into Google often finds something useful). You should take a look at ((Troubleshooting KDE Problems)) - the advice there is probably what you'll be told in #kde anyway, so try it first :-). Also, try to make sure that the problem you're having is a problem with KDE and not some other component of your system (for example, a problem with X or with alsa). Of course, if you're not sure, please ask.
  • Make sure that you have Read The Fine Manual and the ((KDE FAQs)). Although not every question is answered there, many are. If you think that your question is a common one that others would like the answer to, you might want to suggest it to the documentation maintainer, or to [kde-doc-english@kde.org].
  • Be prepared to wait! Often, someone will notice your question a little while after you ask it, so waitaround for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
  • If you don't get an answer on #kde, you can also try the channel for your distribution (eg, #suse, #kde-freebsd, etc), or an appropriate mailing list: see http://lists.kde.org .
  • Above all, be patient and polite. Remember that the people who help are all volunteers, and could be spending their time doing other things than helping.

If your problem is with sound in KDE, you might want to first read ((aRts Troubleshooting)). Here are a few tips on asking questions, especially in #kde on Freenode, in a way that is more likely toget answers:

  • Don't ask to ask, just ask: #kde is a user support channel, so we expect your questions - go right ahead :-).
  • Be ready with any relevant details about your system: What distribution (what version?), what version of KDE you're running, how you installed it and so on. You probably won't need to give all of this information straight away, but you should have it available in case someone asks.
  • Try to do some troubleshooting yourself before asking: Google is your friend (entering error messages into Google often finds something useful). You should take a look at ((Troubleshooting KDE Problems)) - the advice there is probably what you'll be told in #kde anyway, so try it first :-). Also, try to make sure that the problem you're having is a problem with KDE and not some other component of your system (for example, a problem with X or with alsa). Of course, if you're not sure, please ask.
  • Make sure that you have Read The Fine Manual and the ((KDE FAQs)). Although not every question is answered there, many are. If you think that your question is a common one that others would like the answer to, you might want to suggest it to the documentation maintainer, or to [kde-doc-english@kde.org].
  • Be prepared to wait! Often, someone will notice your question a little while after you ask it, so waitaround for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
  • If you don't get an answer on #kde, you can also try the channel for your distribution (eg, #suse, #kde-freebsd, etc), or an appropriate mailing list: see http://lists.kde.org .
  • Above all, be patient and polite. Remember that the people who help are all volunteers, and could be spending their time doing other things than helping.

If your problem is with sound in KDE, you might want to first read ((aRts Troubleshooting)). Here are a few tips on asking questions, especially in #kde on Freenode, in a way that is more likely toget answers:

  • Don't ask to ask, just ask: #kde is a user support channel, so we expect your questions - go right ahead :-).
  • Be ready with any relevant details about your system: What distribution (what version?), what version of KDE you're running, how you installed it and so on. You probably won't need to give all of this information straight away, but you should have it available in case someone asks.
  • Try to do some troubleshooting yourself before asking: Google is your friend (entering error messages into Google often finds something useful). You should take a look at ((Troubleshooting KDE Problems)) - the advice there is probably what you'll be told in #kde anyway, so try it first :-). Also, try to make sure that the problem you're having is a problem with KDE and not some other component of your system (for example, a problem with X or with alsa). Of course, if you're not sure, please ask.
  • Make sure that you have Read The Fine Manual and the ((KDE FAQs)). Although not every question is answered there, many are. If you think that your question is a common one that others would like the answer to, you might want to suggest it to the documentation maintainer, or to [kde-doc-english@kde.org].
  • Be prepared to wait! Often, someone will notice your question a little while after you ask it, so waitaround for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
  • If you don't get an answer on #kde, you can also try the channel for your distribution (eg, #suse, #kde-freebsd, etc), or an appropriate mailing list: see http://lists.kde.org .
  • Above all, be patient and polite. Remember that the people who help are all volunteers, and could be spending their time doing other things than helping.

If your problem is with sound in KDE, you might want to first read ((aRts Troubleshooting)). Here are a few tips on asking questions, especially in #kde on Freenode, in a way that is more likely toget answers:

  • Don't ask to ask, just ask: #kde is a user support channel, so we expect your questions - go right ahead :-).
  • Be ready with any relevant details about your system: What distribution (what version?), what version of KDE you're running, how you installed it and so on. You probably won't need to give all of this information straight away, but you should have it available in case someone asks.
  • Try to do some troubleshooting yourself before asking: Google is your friend (entering error messages into Google often finds something useful). You should take a look at ((Troubleshooting KDE Problems)) - the advice there is probably what you'll be told in #kde anyway, so try it first :-). Also, try to make sure that the problem you're having is a problem with KDE and not some other component of your system (for example, a problem with X or with alsa). Of course, if you're not sure, please ask.
  • Make sure that you have Read The Fine Manual and the ((KDE FAQs)). Although not every question is answered there, many are. If you think that your question is a common one that others would like the answer to, you might want to suggest it to the documentation maintainer, or to [kde-doc-english@kde.org].
  • Be prepared to wait! Often, someone will notice your question a little while after you ask it, so waitaround for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
  • If you don't get an answer on #kde, you can also try the channel for your distribution (eg, #suse, #kde-freebsd, etc), or an appropriate mailing list: see http://lists.kde.org .
  • Above all, be patient and polite. Remember that the people who help are all volunteers, and could be spending their time doing other things than helping.

If your problem is with sound in KDE, you might want to first read ((aRts Troubleshooting)). Here are a few tips on asking questions, especially in #kde on Freenode, in a way that is more likely toget answers:

  • Don't ask to ask, just ask: #kde is a user support channel, so we expect your questions - go right ahead :-).
  • Be ready with any relevant details about your system: What distribution (what version?), what version of KDE you're running, how you installed it and so on. You probably won't need to give all of this information straight away, but you should have it available in case someone asks.
  • Try to do some troubleshooting yourself before asking: Google is your friend (entering error messages into Google often finds something useful). You should take a look at ((Troubleshooting KDE Problems)) - the advice there is probably what you'll be told in #kde anyway, so try it first :-). Also, try to make sure that the problem you're having is a problem with KDE and not some other component of your system (for example, a problem with X or with alsa). Of course, if you're not sure, please ask.
  • Make sure that you have Read The Fine Manual and the ((KDE FAQs)). Although not every question is answered there, many are. If you think that your question is a common one that others would like the answer to, you might want to suggest it to the documentation maintainer, or to [kde-doc-english@kde.org].
  • Be prepared to wait! Often, someone will notice your question a little while after you ask it, so waitaround for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
  • If you don't get an answer on #kde, you can also try the channel for your distribution (eg, #suse, #kde-freebsd, etc), or an appropriate mailing list: see http://lists.kde.org .
  • Above all, be patient and polite. Remember that the people who help are all volunteers, and could be spending their time doing other things than helping.

If your problem is with sound in KDE, you might want to first read ((aRts Troubleshooting)). Here are a few tips on asking questions, especially in #kde on Freenode, in a way that is more likely toget answers:

  • Don't ask to ask, just ask: #kde is a user support channel, so we expect your questions - go right ahead :-).
  • Be ready with any relevant details about your system: What distribution (what version?), what version of KDE you're running, how you installed it and so on. You probably won't need to give all of this information straight away, but you should have it available in case someone asks.
  • Try to do some troubleshooting yourself before asking: Google is your friend (entering error messages into Google often finds something useful). You should take a look at ((Troubleshooting KDE Problems)) - the advice there is probably what you'll be told in #kde anyway, so try it first :-). Also, try to make sure that the problem you're having is a problem with KDE and not some other component of your system (for example, a problem with X or with alsa). Of course, if you're not sure, please ask.
  • Make sure that you have Read The Fine Manual and the ((KDE FAQs)). Although not every question is answered there, many are. If you think that your question is a common one that others would like the answer to, you might want to suggest it to the documentation maintainer, or to [kde-doc-english@kde.org].
  • Be prepared to wait! Often, someone will notice your question a little while after you ask it, so waitaround for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
  • If you don't get an answer on #kde, you can also try the channel for your distribution (eg, #suse, #kde-freebsd, etc), or an appropriate mailing list: see http://lists.kde.org .
  • Above all, be patient and polite. Remember that the people who help are all volunteers, and could be spending their time doing other things than helping.

If your problem is with sound in KDE, you might want to first read ((aRts Troubleshooting))


Content is available under Creative Commons License SA 4.0 unless otherwise noted.