The way you present your content is also important. There is no absolute "most appropriate" way to present a content, but one has to choose what is better depending on who are the readers and what is the goal of the discussion.
In the case of technical discussion, what most people want is to quickly and efficiently find the best solution to a problem. Follows a list of style suggestions for contributing to a technical discussion:
Put the main point at the beginning, and the long details later.
If people have to read through lots of text in order to get to the main point, they are likely to just skip the message if they are busy.
Hook the readers in by stating the main point right away instead of trying to create expectation and surprise.
You can even avoid posting about the long details and put them on the Debian wiki instead.
Talk with code or patches.
Wherever it is possible to use them, code or patches are the most efficient way of conveying technical information, and can also be used, applied or tested directly.
Often patches are the preferred writing style: technical people tend to like to read code more than they like to read English, except when English is written inside code comments.
Writing code is also useful to clear your own mind: while writing a piece of example code to show a problem, it is quite common to find the solution or to reframe the problem in a clearer way.
Finally, some things are harder to explain in English rather than with code: so if there is something you have problems saying in English, try to say it using your favourite programming language.
Point to existing resources.
If a problem has already been solved or a point has already been made, you can greatly condense your message by just posting a link to it.
If the existing resource is not good enough, try to improve it: either in place (for example, if it is in a wiki) or by posting your further comments together with the link.
Use a plain and simple style
People should spend their time answering your question or using your information, rather than understanding it.
To help it, try to keep formalities to a minimum and avoid confusing people with rhetoric:
ask questions without asking if you can ask or apologising for asking. This may be impolite in real life, but it is generally the preferred way online.
if you are not a native English speaker, you don't need to apologise for it: a minimal knowledge of the language is enough, as long as your mind is clear and you use a plain style.
If English makes it really hard for you, you can look for a Debian list where they speak your language. Many of them are available in the list of TODO.
Only ask a question if you want to know the answer: rhetorical questions often come across as unnecessarily confrontational, so avoid them if you can. If you have an opinion, just state it and ask for correction if needed.
There is of course place for advanced uses of language and style in Debian: you can indulge in creative writing in places like the debian-curiosa mailing list, or on Planet Debian.