Quoting from Paul's post to [quagga-users 7271] (original post is available here)
"Well, we didn't want to mention it..
On a more serious note, getting good answers on email lists often
depends on asking good questions. In particular, the easier it is for
someone to answer the question(s), the more likely it is an answer will
be given.
[...cut...]
- More specific questions are easier to answer than general, vague,
and/or broad questions, so try ask specific questions.
- if you have a general question, try at least include some
specific questions with it that cover aspects of your general
question
- If you are asking about a problem, it is important to give the right
information
- which version(s) of Quagga
- which OS, and version(s)
- Logs and command output are very useful. However:
- Try give background information
- Ie a network diagramme
- Try to remember that your IP addresses wont mean as much to
general readership
- don't obfuscate addresses, but if you must, please at
least preserve as many of the least-significant digits as are
needed to distinguish between them.
- Try to annotate the information, it's very little work to do
but it makes it much easier for readers to follow e.g.:
"Here it starts up:"
"Here is where the cable was pulled:"
"Here is where I think the problem starts:"
- Try present information in chronological order
- When editing information for above presentational purposes,
preserve the raw form of it, just in case it is needed.
- Try frame questions about problems in terms of:
- What you expected to happen
- What you observed to occur
- What the difference is
- What problem it causes
(sometimes those points aren't made clear to readers)"