The art of getting help

We use a lot of open source software at work, and I subscribe to user-group lists.

(Some) users of the sub-continent have an amazing ability to annoy user-group lists by posting stuff like:

• I am new. Where do I start? (There is a well setup website with LOTS of examples to get your feet wet AND start swimming)

• This is my situation. Please help. (Without having searched archives)
  

• This is my situation. Send me some code I can use. (Why should someone else do *your* work?)

• Repeated requests for help on the SAME topic. (Open source mailing lists comprise of other users who *volunteer* help and not paid tech-support)

• I am getting an error. Please help. (With no attempt to troubleshoot or debug)
  

• Incoherently asked questions with incomplete information.

Is it too much to expect "engineers" (yes, that is probably what most of them carry in their titles) to be able to post queries that:

• Are clear and concise
• Display what attempts the seeker of help has already made to try and solve the problem - - yes this implies that you DO try and look for a solution instead of running to others for help immediately
• Do not beg for help
• Do not expect a ready made solution that can be swallowed as-is in the next 20 minutes
• Are grammatically coherent?