| | 26 | == Etiquette == |
| | 27 | * Don't ask to ask, just ask. |
| | 28 | * The ideal way to ask the community for help would be to send a detailed email to the mailing list and then refer to that email whilst on IRC. |
| | 29 | * During chat, try to be as precise and as short as possible. Brevity is the key. You can put down the minor details in an email. |
| | 30 | * Often, people might not reply immediately to your query on IRC. It could be because they're busy, they're looking for an answer to your question, or that they simply don't know. Be patient. Also, do not post the question repeatedly within a short time span whilst on chat. |
| | 31 | * If you want to draw the attention of a particular user(s), just prepend your question with their IRC handle. |
| | 32 | * Look up chat logs, the mailing list and wiki prior to asking questions. It's quite possible that your question has been asked and answered already. Google is your friend. |
| | 33 | * Avoid private communication on IRC and email. It is better to send you messages to the public IRC channel and Mailing list. This way more than one person will be able to answer your questions and the answers could be useful for more than one person. |
| | 34 | * Do not paste code in chat. Use a pastebin and put in the link to post in the channel. Short snippets of code are better, with comments in case you need help with coding. Snippets of code in email are also good, but again, brevity is the key. It may not be incovenient to go over lines and lines of code in email. |
| | 35 | * Don't post emails to multiple mailing lists. Most community members are subscribed to multiple lists and getting the same email many times isn't helpful for them. |
| | 36 | * Please respect the time of all members of the community. What is urgent for you may not be a priority for anyone else. |
